[Chore][Repository] Add overview hero image below README language switcher

[miso-develop]

Related

• [Chore][Repository] Make GitHub metadata and README product-facing #192 — product-facing README baseline

Owner

• ACTIVE_ROLE: implementation
• DOMAIN: infra

State

READY_FOR_REVIEW

Baseline

Specification baseline: main = d575e70fd7e07e9f2774762b5636cb74e94ed42d.

At Specification time:

• open PRs: none;
• README.md language switch is line 3: **English** | [日本語](README.ja.md);
• README.ja.md language switch is line 3: [English](README.md) | **日本語**;
• neither README currently displays a hero/overview image.

Human-provided approved image

Use the image supplied by the human owner with this request.

Approved source-asset identity:

• source filename: top.jpg
• format: JPEG
• dimensions: 840 × 420
• byte size: 122,915 bytes
• SHA-256: 215ed9c6ffe29ec7ba302dc830569286b188bcfb3c9885f4e4b8b48be3556b42

The image is intended for public repository presentation and contains only synthetic/non-secret example content.

Implementation must use this approved image, not recreate or substitute a visually similar image.

If retrieving it from the originating chat/File Library, verify the SHA-256 above before committing. If the exact approved asset cannot be obtained in the Implementation environment, do not substitute another image; record the dependency and return for the exact asset.

Objective

Display the approved M5Authenticator overview image immediately below the language-switch row in both the English and Japanese GitHub READMEs.

Both languages must reference the same committed image file.

Asset path

Commit the approved JPEG under:

docs/assets/m5authenticator-overview.jpg

Create docs/assets/ if it does not already exist.

Do not duplicate separate EN/JA copies.

The committed image must retain:

• 840 × 420 dimensions;
• the approved visual content;
• no added metadata containing private/local filesystem information.

Byte-for-byte preservation of the supplied JPEG is preferred. If tooling strips non-visual metadata, the visible pixels/content must remain unchanged and implementation must record that transformation; do not crop, redraw, regenerate, recolor, or add text.

README placement

README.md

Current beginning:

# M5Authenticator

**English** | [日本語](README.ja.md)

M5Authenticator is ...

Required result:

# M5Authenticator

**English** | [日本語](README.ja.md)

![M5Authenticator overview](docs/assets/m5authenticator-overview.jpg)

M5Authenticator is ...

README.ja.md

Current beginning:

# M5Authenticator

[English](README.md) | **日本語**

M5Authenticatorは...

Required result:

# M5Authenticator

[English](README.md) | **日本語**

![M5Authenticatorの概要](docs/assets/m5authenticator-overview.jpg)

M5Authenticatorは...

The image must therefore be the first content immediately after the language selector in both READMEs, with normal blank-line Markdown separation and no additional heading/caption block inserted above it.

Rendering requirements

• Use a repository-relative path so the image renders on GitHub branch/default README views.
• Prefer standard Markdown image syntax as specified above.
• Do not use a remote image host, runtime URL, data URI, GitHub Issue attachment URL, or CDN.
• Do not make the image clickable unless separately requested.
• Preserve normal responsive GitHub image behavior; do not hard-code a viewport-specific width.
• English and Japanese READMEs must remain structurally parallel.
• Existing README copy, Web link, Security links, and documentation links remain unchanged except for the image insertion.

Security / repository constraints

• The committed image must contain no real TOTP secret, QR payload, Device ID, Recovery Passphrase/Package, keys, production account metadata, or credential-bearing EXIF/comment data.
• The visible example in the approved image is synthetic and may remain as supplied.
• Run the repository security scan against the binary addition.
• Do not modify SECURITY.md, AGENTS.md, product code, Web runtime, firmware, release workflows, or repository About metadata for this Task.

Human Gate before Integration

HUMAN_GATE_REQUIRED before any merge to main.

After Implementation and independent Review are complete, Integration must stop before merge and obtain Human confirmation on the exact PR head.

Human Gate must verify on GitHub-rendered README views, using the exact candidate head:

• README.md shows the approved overview image immediately below the language selector;
• README.ja.md shows the same image immediately below the language selector;
• image content is the intended human-supplied asset, not a substituted/re-generated image;
• image rendering is not broken and the repository-relative path resolves correctly;
• the image is visually acceptable at normal GitHub README width;
• surrounding README structure/content remains correct in both languages.

The exact PR head validated by Human must match the head handed to Integration. If the PR head changes after Human Gate, the Gate is stale and must be rerun.

Integration must not merge #211 until:

1. independent Review has passed;
2. required CI/security checks are green;
3. the exact-head Human Gate has passed.

Acceptance

• Exact approved overview image is committed once at docs/assets/m5authenticator-overview.jpg.
• Image dimensions are 840 × 420 and visual content matches the human-supplied asset.
• README.md renders that image immediately below the English/Japanese language selector.
• README.ja.md renders the same image immediately below the language selector.
• EN alt text is M5Authenticator overview.
• JA alt text is M5Authenticatorの概要.
• No extra heading/caption appears between language selector and image.
• Both README files otherwise retain current product-facing structure/content.
• Image uses a repository-relative path and no external image dependency.
• Security scan / applicable documentation checks pass.
• Diff is limited to the one approved image asset plus README.md and README.ja.md.
• Independent Review is performed before Integration; Implementation does not merge its own PR.
• Exact-head Human Gate passes before any merge to main.
• Any PR-head change after Human Gate invalidates the prior Human Gate and requires re-validation.

Collision / coordination

No open PR exists at Specification time.

Implementation must re-check Issues/PRs/branches before claim, with ownership of:

• README.md;
• README.ja.md;
• docs/assets/m5authenticator-overview.jpg.

References

• [Chore][Repository] Make GitHub metadata and README product-facing #192
• README.md
• README.ja.md
• SECURITY.md

[miso-develop]

HANDOFF
FROM: specification
TO: implementation
DOMAIN: infra
ISSUE: #211
STATE: READY_FOR_IMPLEMENTATION

[miso-develop]

Human Gate requirement added

Per Human instruction, #211 now requires an exact-head Human Gate before any merge to main.

Required flow:
Implementation → independent Review → Integration/Human Gate → merge.

The Human Gate must verify the rendered EN/JA README image placement and visual result on the exact candidate head. Any subsequent head change makes the prior Human Gate stale and requires re-validation.

STATE remains READY_FOR_IMPLEMENTATION.

[miso-develop]

CLAIM
ROLE: implementation
DOMAIN: infra
ISSUE: #211
STATE: ACTIVE
BASE: d575e70
BRANCH: task/211
COLLISION_CHECK: clear; no open PR owns README.md, README.ja.md, or docs/assets/m5authenticator-overview.jpg.

[miso-develop]

Implementation blocker — exact approved image asset unavailable

Specification requires the exact Human-approved source asset:

• filename: top.jpg
• JPEG
• 840 × 420
• 122,915 bytes
• SHA-256: 215ed9c6ffe29ec7ba302dc830569286b188bcfb3c9885f4e4b8b48be3556b42

Implementation searched the available File Library using:

• exact filename top.jpg;
• M5Authenticator / 840×420 descriptors;
• exact approved SHA-256;
• recent upload navigation for 2026-09-18 through 2026-09-19.

The exact binary was not available from the accessible file source. No visually similar image was substituted or generated, as explicitly prohibited by #211.

No README or repository asset mutation has been made. Branch task/211 remains at the exact baseline d575e70fd7e07e9f2774762b5636cb74e94ed42d.

Required next input: provide/upload the exact approved top.jpg asset so Implementation can verify its byte size, dimensions, and SHA-256 before committing it.

[miso-develop]

HANDOFF
FROM: implementation
TO: human
DOMAIN: infra
ISSUE: #211
STATE: BLOCKED_DEPENDENCY

[miso-develop]

HANDOFF
FROM: implementation
TO: human
ISSUE: #211
STATE: BLOCKED_DEPENDENCY

[miso-develop]

Human supplied the exact approved top.jpg asset. Implementation verification passed before repository mutation:

• JPEG
• 840 × 420
• 122,915 bytes
• SHA-256 215ed9c6ffe29ec7ba302dc830569286b188bcfb3c9885f4e4b8b48be3556b42

The asset will be preserved byte-for-byte at docs/assets/m5authenticator-overview.jpg. The prior dependency blocker is resolved; implementation resumes on existing task/211, which still matches current main d575e70fd7e07e9f2774762b5636cb74e94ed42d.

[miso-develop]

HANDOFF
FROM: implementation
TO: review
DOMAIN: infra
ISSUE: #211
PR: #212
HEAD: 6de536c
STATE: READY_FOR_REVIEW

[miso-develop]

Integration Human Gate

Exact candidate:

• PR: docs: add README overview hero image (#211) #212
• HEAD: 6de536c9be8c2327473295f4357dd9d98c9c0a69
• current main / PR base: d575e70fd7e07e9f2774762b5636cb74e94ed42d

Pre-gate checks:

• independent Review completed with no blocking implementation finding;
• Security #940: SUCCESS;
• Foundation #937: SUCCESS;
• PR open, non-draft, mergeable;
• no unresolved review threads;
• PR docs: add README overview hero image (#211) #212 is the only open PR;
• changed files are exactly the EN/JA READMEs plus the approved overview JPEG;
• committed JPEG identity matches the approved Human asset byte-for-byte.

Required Human visual verification on the GitHub-rendered exact candidate:

1. README.md shows the approved overview image immediately below the language selector;
2. README.ja.md shows the same image immediately below its language selector;
3. image rendering is not broken;
4. image is visually acceptable at normal GitHub README width;
5. surrounding README structure/content remains correct in both languages.

Any PR-head change after this verification invalidates the Human Gate.

HANDOFF
FROM: integration
TO: human
ISSUE: #211
PR: #212
HEAD: 6de536c
STATE: HUMAN_GATE_REQUIRED

[miso-develop]

HUMAN_GATE_PASS

Exact validated HEAD: 6de536c9be8c2327473295f4357dd9d98c9c0a69

Human verification of GitHub-rendered candidate README views:

• README.md: PASS
• README.ja.md: PASS
• approved overview image appears immediately below the language selector in both
• same intended approved asset is rendered in both
• repository-relative image rendering is not broken
• visual presentation is acceptable at normal GitHub README width
• surrounding README structure/content is correct in both languages

Exact-head recheck after Human confirmation:

• PR HEAD unchanged
• current main still equals PR base
• Security #940: SUCCESS
• Foundation #937: SUCCESS
• PR open, non-draft, mergeable
• no unresolved review threads
• PR docs: add README overview hero image (#211) #212 is the only open PR

STATE: HUMAN_GATE_PASS