{"label":"complete-edition-v2","description":"Preserved synthetic showcase edition with exact media references.","published_at_unix_micros":1793344789253432,"canonical_path":"/blog/m7-after-complete-technical-feature-guide/versions/complete-edition-v2","snapshot":{"body":"\nThis is the complete, section-by-section Stage feature inspection specimen. Each numbered feature starts with H1 and describes its supported forms, example and inspection action. Both technical and academic editions share this exact body.\n\n# Feature 01: Page Identity, Cover, and Metadata\n\nBoth editions use the same body, cover, SEO overrides, tags, and feature examples. Only editorial identity, classification, and academic-only publication metadata differ. The cover is an exact image-version pin, not an external image URL. The visible title and supplied SEO title are separate fields.\n\n| Field | What this example supplies |\n| --- | --- |\n| Cover | Original local synthetic PNG with alternative text |\n| Summary | An explicit short introduction |\n| SEO | A supplied title and description |\n| Classification | Technical or academic |\n| Tags | Three shared inspection tags |\n\n**Inspect:** Compare the page title, cover, summary, browser-tab title and classification between the two editions. Metadata fallback is an omission case and cannot coexist with an explicit override in the same field; compare the separate fallback article linked later.\n\n# Feature 02: H1 Sections and Heading Hierarchy\n\nEvery feature starts with a level-one heading, as requested. Markdown also supports heading levels two through six. This section intentionally demonstrates the remaining levels inside one feature.\n\n## Level Two\n\nA subsection paragraph.\n\n### Level Three\n\nA smaller topic.\n\n#### Level Four\n\nA detailed note.\n\n##### Level Five\n\nA deeply nested note.\n\n###### Level Six\n\nThe final supported heading level.\n\n**Inspect:** Compare visual hierarchy and heading anchors. Every following Feature heading returns to H1.\n\n# Feature 03: Text Formatting and Inline Code\n\nSafe document nodes support ordinary text, emphasis, strong text, strikethrough, inline code and paragraphs. Raw authored HTML and arbitrary trusted-page JavaScript are not supported.\n\nThis is ordinary text, *emphasized text*, **strong text**, and ~~superseded text~~. An identifier such as `publication_revision_id` is inline code.\n\nA separate paragraph checks vertical rhythm. Symbols such as < and > remain ordinary readable text when they are not authored HTML.\n\n**Inspect:** Compare contrast, spacing, wrapping and light/dark appearance.\n\n# Feature 04: Ordered, Nested, and Unordered Lists\n\nLists support ordered and unordered forms with nesting. A nested explanation is content structure, not an interactive tree widget.\n\n1. Read the feature explanation.\n - Inspect the first example.\n - Compare its alternative representation.\n2. Record an observation.\n 1. Identify the section.\n 2. Describe the behavior.\n3. Continue to the next feature.\n\n**Inspect:** Inspect indentation, numbering and narrow-width wrapping.\n\n# Feature 05: Task Lists\n\nTask-list items retain checked or unchecked state as read-only authored content. They are not a persisted personal to-do application.\n\n- [x] Example content was authored.\n- [x] The feature is present in this article.\n- [ ] Owner inspection is complete.\n- [ ] Reported application issues have been resolved.\n\n**Inspect:** The checkboxes should represent the source state; their presence does not claim that your review passed.\n\n# Feature 06: Blockquotes, Separators, and Footnotes\n\nBlockquotes, thematic breaks, footnote references and footnote definitions are supported document structures. References remain local to the article.\n\n> A feature specimen is useful when its purpose and limitations are visible.\n\n---\n\nThe first supporting note describes the data.[^synthetic] The second distinguishes saved outputs from execution.[^saved]\n\n**Inspect:** Follow both footnote references and compare quote styling with ordinary paragraphs.\n\n# Feature 07: Links and Navigation\n\nThe allowed source link forms include relative links, HTTP(S) links and mailto. External destinations are not fetched by the backend merely because a link exists. A mailto example does not provision an inbox.\n\n[Return to the blog](/blog) · [Browse M7 After](/blog?tag=m7-after) · [Reserved example website](https://example.org/) · [Reserved email example](mailto:showcase@example.invalid)\n\n[Jump to the image feature](#feature-10-inline-images-and-captions).\n\n[Compare explicit SEO fallback](/blog/m7-after-useful-defaults-without-a-cover).\n\n**Inspect:** Use normal navigation and the browser Back control. External links are references, not imported content.\n\n# Feature 08: Markdown Tables\n\nTables retain headers and rows. A wide table should be inspectable on a narrow screen without discarding its cells.\n\n| Format | Source | Activation | Download | Authority |\n| --- | --- | --- | --- | --- |\n| Chart | Pinned CSV/JSON | Explicit | Dataset retained | Public media only |\n| Notebook | Pinned notebook | Explicit | Source retained | Saved outputs only |\n| PDF | Pinned PDF | Explicit | File retained | Static pages |\n| Model | Closed GLB | Explicit | File retained | No external resources |\n\n**Inspect:** Compare header styling, column alignment, scrolling and text wrapping.\n\n# Feature 09: Fenced Code and Language Labels\n\nCode blocks are inert source text. Language-labelled code is not an executable playground, and a Mermaid fence is not the Mermaid component.\n\n```python\nvalues = [2, 4, 6, 8]\nprint(sum(values))\n```\n\n```rust\npub fn answer() -> i32 { 42 }\n```\n\n```javascript\nconsole.log(\"Inert source example\");\n```\n\n```mermaid\nflowchart TD\nA[Source] --> B[Still source text]\n```\n\n**Inspect:** Inspect preservation of newlines, indentation, language presentation and long-line behavior. No code above should run.\n\n# Feature 10: Inline Images and Captions\n\nImage supports an exact media identity and file version, meaningful alternative text, an optional caption and explicit loading. These original PNGs are local synthetic materials. The cover and inline image are different presentation surfaces.\n\n\n\n\n\n**Inspect:** Load both images, compare captions and use the exact public-image download.\n\n# Feature 11: Decorative Images\n\nA decorative image explicitly opts out of conveying essential information through alternative text. It still uses a pinned ready media version; decorative status is not permission for missing meaningful text on other images.\n\n\n\n**Inspect:** Compare the authored decorative state with the meaningful alt text in Feature 10.\n\n# Feature 12: Immutable Media Versions\n\nOne asset identity can have multiple immutable file versions. These two examples share an identity but intentionally select versions one and two. Loading the newer file must not overwrite an older pinned reference.\n\n\n\n\n\n**Inspect:** Compare the two illustrations and their download paths. No existing article was repinned by creating these guides.\n\n# Feature 13: Local Video, Poster, Captions, and Transcript\n\nVideo supports pinned local media, native playback controls, a poster pin, a caption pin and a separate transcript pin. The six-second H264/AAC material is an original still-image video with silent audio. A known ingestion gap remains: .vtt uploads are rejected, so WebVTT bytes are currently stored as supported plain-text source. Caption display is not claimed to work around that MIME gap.\n\n