Skip to main content

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]​

Changed​

  • Documented table authoring guidance: prefer 2 columns, use 3 only when necessary, and avoid 4+ columns on mobile.
  • Documented SCS (SEO Content Systems) integration: ACF wpstrategist-seo-architecture and wpstrategist-review-gate plugins installed on id86.net; content_type (hub/pillar/cluster/supporting), primary_keyword, semantic_tags, parent post IDs, and wpw_* review-gate fields now available. SCS front matter is a superset of the ID86 contract; brief/article markers (<!-- scs:brief --> / <!-- scs:article -->) documented in Markdown authoring and content sync pipeline. SCS-managed posts are keyed by scs_pid in addition to _id86_* meta. PHP memory_limit raised 128M → 512M on GC-US-M10 to unblock WP-CLI/SCS commands.

[2026-11-04] - SCS alignment: ACF contract, review gate, Phase 0 baseline​

Added​

  • ACF Pro 6.7.0.2 installed and activated on id86.net (GC-US-M10) from the local paid-asset archive; wpstrategist-seo-architecture plugin (copied from wpwhite.com reference) registered the group_seo_architecture field group (content_type, hub_parent, pillar_parent, cluster_parent, primary_keyword, semantic_tags).
  • Portable wpstrategist-review-gate plugin installed and activated; group_wpw_review_gate registered (wpw_review_status, wpw_reviewer, wpw_review_date, wpw_review_scope, wpw_review_checklist, wpw_review_notes).
  • Phase 0 baseline artifacts in the SCS repo: reports/lint-baseline.json + reports/lint-summary.txt (21,058 docs; 1,036 errors, 7,489 warnings), reports/corpus-manifest.csv (21,058 rows; 0 missing required fields, 488 duplicate slugs, 1,334 duplicate titles, 16 tag overflows), reports/corpus-audit-summary.txt, reports/pid-check.txt.
  • Post excerpt made mandatory and separate from SEO description: added Excerpt column to content-inventory.csv, excerpt: frontmatter field, --excerpt to new-doc.py, validation in validate-inventory.py, and docs in content-register, seo-metadata, content-sync-pipeline.
  • CSV schema extensions (P1.5–P1.7): added decision/GOS/SERP-provenance fields to keyword-research.csv; added cluster model, publishing, QA, measurement, author, and access_tier fields to content-inventory.csv; new-doc.py now populates publishing fields and access_tier at scaffold time; validate-inventory.py enforces excerpt. All 13 inventory rows consistent.
  • SureMembers access levels: added access_level column (SureMembers group slug(s), pipe-separated) to content-inventory.csv for premium gating; new-doc.py accepts --access-level; validate-inventory.py warns when a premium row has no access level.
  • Phase 2 automation scripts: audit_corpus.py, scaffold_csvs.py, convert_frontmatter.py, seed_research.py, validate_all.py, score_keywords.py, check_brief.py built in the SCS repo. Full corpus converted (21,058 files → SCS scs-content/v3 front matter with brief/article markers); CSVs scaffolded (20,212 unique PIDs from 21,058 files, 846 duplicate PIDs collapsed); pids.reserved corrected to ID 51127. All 3 test suites pass (54 + 3 + 17).
  • Phase 3 site contract: id86-scs-cache-purge mu-plugin installed (LiteSpeed + OPcache purge for SCS-managed posts); SCS bridge now writes _id86_content_type from front matter content_type for Meilisearch indexing; dry-run publish verified on ID-0002 (clean payload, 102 Gutenberg blocks); ACF Pro license activated (ALTD key, order 58198).
  • Phase 4 research/brief/QA gates: research README.md + SCS-style templates (README.md, serp.md) added to research/templates/; ensure-research-folders.py updated to create SCS subfolders and seed templates; all 21,058 files verified to carry both brief/article markers in correct order; brief-depth mapping documented; validate-inventory.py gained QA soft checks; default author profile seeded and author_id populated; links.csv created with SCS schema.
  • Phase 5 pre-flight: dedupe (512 slugs resolved, 1,310 titles moved), fix_docs (19,384 files), fix_links applied. Lint improved from 1,036 errors/7,489 warnings to 66 errors/3,685 warnings. Gating data prepared (20,212 rows: decision=go, brief=Approved, status=Writing/QA). Pilot publish (3 files: ID-0002/0005/0007 → posts 4423–4425) verified with _id86_content_type meta. Full corpus publish pending review.
  • Phase 6 measurement & refresh: gsc_import.py (GSC CSV → performance.csv), refresh_queue.py (decay detection: position drop ≥3, click decline ≥30%), and monthly review runbook documented. monthly-review-runbook.mdx added to 07-seo-analytics/.
  • SCS integration notes added to 08-cheatsheet/markdown-authoring.mdx, 04-wp-ops/content-sync-pipeline.mdx, 01-overview/overview.mdx, and index.mdx.

Changed​

  • PHP memory_limit raised from 128M to 512M in /usr/local/lsws/lsphp80/etc/php/8.0/litespeed/php.ini on GC-US-M10 to unblock WP-CLI/SCS commands that bootstrap fluentformpro.
  • config/pids.reserved flagged stale: high-water mark ID 1 vs corpus max ID-51127 — must be corrected before Phase 2 scaffolding.

Verified​

  • scs wp inspect --workspace id86 --site id86 returns WP 7.1.4, home https://id86.net, ACF active with both field groups.
  • ACF field groups confirmed via acf_get_field_groups() over WP-CLI (memory-limit override).
  • All 21,058 corpus files have complete front matter; content types: cheatsheet 8,238 · checklist 5,783 · reference 4,903 · glossary 2,134. All status draft.
  • Workspace id86 row counts: keywords=1, clusters=1, briefs=1, links=0, publishing=1, performance=1, research=1, md=21,058 (CSVs hold only sample rows; 21k files unregistered).

[2026-11-03] - Fix id86.net contact form front-end rendering​

The /contact-us/ page rendered the literal shortcode [id86_contact_form] because the active child theme never registered it. Restored the production-compatible theme file and added scoped contact-form support.

Changed​

  • wp-content/themes/id86/functions.php (live on GC-US-M10): restored the production-compatible 527-line variant and added id86_verify_turnstile_token(), Reoon verification helpers, CSV storage helpers, owner email notification, and id86_render_contact_form() with add_shortcode("id86_contact_form", ...).
  • Turnstile widget now renders using id86_turnstile_site_key.

Verified​

  • id86_contact_form shortcode is registered.
  • https://id86.net/contact-us/ returns HTTP 200 with no literal shortcode.
  • Form fields, nonce, honeypot, and Turnstile widget render.
  • Invalid Turnstile token is rejected before storage/notification.
  • Homepage reference cards and archive type labels restored.
  • LiteSpeed, PHP OPcache, and Cloudflare edge caches purged.

Caveats​

  • The local theme repository still contains a newer 1094-line functions.php; reconcile before using theme/deploy.sh.
  • Only owner email notification is implemented; Zammad/Telegram functions are not present in the live theme.

[2026-11-03] - Align Meilisearch documentation with plugin development​

Reviewed the meilisearch-id86 git history (through v1.0.2) against the site docs and corrected drift so the documentation reflects the standalone plugin rather than the legacy child-theme integration.

Changed​

  • 03-content/meilisearch-search.mdx: rewrote to document plugin layout, index building, REST API, filter syntax (topic:/category:/cat:, tag:/tags:, type:/content_type:, shorthand :value), frontend client, header trigger restoration, admin settings, and maintenance.
  • 02-design-system/search-palette.mdx: palette now documented as rendered by the plugin; trigger registration updated to Search_UI::register_header_trigger().
  • 02-design-system/hero-section.mdx, 02-design-system/css-system.mdx: asset paths updated from fusejs-search/child theme to meilisearch-id86.
  • 05-development/navigation-and-menus.mdx: GeneratePress modal removal attributed to the plugin.
  • 03-content/content-model.mdx: content-type registry source of truth updated to the plugin.
  • 10-development/changelog.md: filter builder/JS references updated to the plugin.

Verified​

  • Docusaurus build build:id86.net completed successfully.

[1.0.2] - 2026-11-02​

Changed​

  • Improved mobile table and code-block rendering while preserving semantic layout: tables use table-layout: auto with max-content width, the first column stays pinned, table code wraps on phones, code blocks keep horizontal scroll, and an edge fade plus “Swipe to view more →” cue appears only when overflow exists.
  • Updated the article-content JS to detect overflow for tables and Code Block Pro blocks; deployed the CSS/JS to the active id86 theme as version 1.28 and purged LiteSpeed/WordPress caches.
  • Updated related documentation in 02-design-system/css-system.mdx, 02-design-system/templates.mdx, 02-design-system/task-checklists.mdx, 03-content/article-body-elements.mdx, and 04-wp-ops/code-block-rendering.mdx.

[1.0.1] - 2026-11-02​

Shortened the id86.net search placeholder from Search docs... (filter by tech, example :docker) to Search docs... (e.g. :docker) so it no longer clips inside the mobile hero input, and corrected the hint wording (the shorthand matches tag, topic, or content type). Updated the plugin source, the live plugin file, GP Element 4090, and the docs examples.

Changed​

  • meilisearch-id86 plugin inc/class-search-ui.php (hero + palette inputs).
  • Live wp-content/plugins/meilisearch-id86/inc/class-search-ui.php on GC-US-M10.
  • GP Element 4090 (ID86 Hero Search) and revisions 4316, 4421.
  • 02-design-system/hero-section.mdx, 02-design-system/search-palette.mdx: placeholder examples.
  • Plugin CHANGELOG.md: Unreleased entry.

Verified​

  • grep on the remote plugin file and GP Element 4090 shows only placeholder="Search docs... (e.g. :docker)".
  • Live page (https://id86.net) renders the new placeholder; LiteSpeed + WP cache purged.
  • Contact-form placeholders (your@email.com, Your name) are unrelated and unchanged.

[2026-10-29] - Rename reference content type to quick-reference​

Eliminated the reference content type from the ID86 taxonomy and replaced it with quick-reference, aligning the docs with the mission/vision emphasis on concise, actionable, fast-to-apply answers. Updated the type registry, badge labels, mental model, examples, CLI flags, sync defaults, and inventory display rows. Legacy instant-documentation/reference values are now documented as migrating to quick-reference.

Changed​

  • 01-overview/read-me.md, 03-content/content-types.mdx, 03-content/content-model.mdx, 03-content/content-register.mdx, 04-wp-ops/content-sync-pipeline.mdx, 06-conversion/monetization.mdx, 07-seo-analytics/glossary-seo.mdx, 08-cheatsheet/markdown-authoring.mdx, 08-cheatsheet/scripts-commands.mdx, 08-cheatsheet/wp-cli.mdx, 02-design-system/templates.mdx, 02-design-system/topic-and-reference-cards.mdx.

Verified​

  • No remaining `reference` content-type values in the docs.
  • Inventory display rows now read Quick Reference.

[2026-10-29] - Restore article-content enqueue (table/CSS)​

Re-added the wp_enqueue_scripts (priority 30) enqueue for article-content-v2.css + article-content.js on single posts that was dropped during the Meilisearch migration. Restores table, code, blockquote, and dark-mode article styling.

[2026-10-29] - Revert article-content dark-mode selector experiment​

Restored the original article-content CSS (dark mode via @media (prefers-color-scheme: dark)) after the tag-pill deploy; only the tag-pill change remains.

Changed​

  • wp-content/themes/id86/css/article-content-v2.css, css/article-content.css: reverted to pre-experiment versions.
  • No change to tag pills.

[2026-10-29] - Brand-aligned single-post tag pills​

Redesigned the legacy single-post tag list (.taxonomy-post_tag) to use the ID86 brand tokens instead of the inherited GP Personale --accent / --contrast-2 variables. Pills now use --id86-mist / --id86-navy with a --id86-blue hover and --id86-sky focus ring, clamp-based gap, rounded 999px radius, Inter 600 type, and automatic DarkReader dark-mode adaptation. No markup change in GP Element 1371.

Changed​

  • wp-content/themes/id86/style.css: replaced legacy Tag List block with brand-aligned pill rules; bumped theme version 1.23 → 1.24.
  • Synced local dev checkout with the live server’s newer sheet-card stretched-link rules before editing.
  • 02-design-system/css-system.mdx: Tag List section remains in the "Featured Image Caption / Tag List" band; line numbers shift slightly.

Verified​

CheckResult
php -l functions.phpclean (no PHP change)
git diff --checkno whitespace errors
Theme version1.24
Dark modetokens swap via DarkReader

[2026-10-28] - Meilisearch migrated to plugin​

Migrated the Meilisearch integration from the child theme/snippets into the standalone meilisearch-id86 plugin. Published to a private GitHub repo (donnyaw/meilisearch-id86) and installed/activated on id86.net; deactivated and deleted the legacy fusejs-search plugin. Removed the Meilisearch block from the child theme.

Changed​

  • New plugin: /wp-content/plugins/meilisearch-id86 (REST proxy, indexing hooks, filter support, UI, admin settings).
  • Plugin source: /home/rezriz/github/Wordpress/wp-dev/plugins/develop-internally/meilisearch-id86
  • Child theme functions.php no longer contains Meilisearch integration (commit 195a34c).
  • Plugin assets (CSS/JS) now self-contained; no longer depends on fusejs-search.

Verified​

  • REST filters still functional after migration (tag:docker, topic:code, combined).
  • Hero search and palette load from the new plugin.
  • php -l and node --check passed.

[2026-10-28] - Finalize homepage card UX​

Finalized homepage "Latest references" cards: removed excerpt, added topic + content type badges, added updated date, whole-card clickable, and natural sizing. Tag/archive cards remain standardized.

Changed​

  • wp-content/themes/id86/functions.php: homepage sheet cards now render topic + content type, updated date, Read more, and whole-card link target.
  • wp-content/themes/id86/style.css: removed fixed sheet-card min-height; added stretched-link and footer rules.
  • 02-design-system/topic-and-reference-cards.mdx: updated Latest Reference Sheets documentation.

Verified​

CheckResult
Homepage live output6 sheet cards with topic + type + title + date + Read more
Whole-card clickCSS stretched link enabled
CacheLiteSpeed + WP purged

[2026-10-28] - Revert homepage latest references to original sheet cards​

Restored the original homepage "Latest references" card design (sheet cards with excerpt) per user preference. Tag/archive permalink cards remain in the standardized archive-card design.

Changed​

  • wp-content/themes/id86/functions.php: id86_latest_sheets again renders id86-sheet-card with excerpt.
  • 02-design-system/topic-and-reference-cards.mdx: restored original Latest Reference Sheets documentation.

[2026-10-28] - Standardize content preview cards​

Standardized homepage "Latest references" cards to use the same archive card design as tag permalinks, and removed the excerpt/text preview from both surfaces. Cards now show category, content type, title, updated date, and Read more.

Changed​

  • wp-content/themes/id86/functions.php: added shared id86_content_card() renderer; removed excerpt from id86_archive_card and homepage latest cards; id86_latest_sheets now emits id86-archive-card markup.
  • 02-design-system/topic-and-reference-cards.mdx: updated Latest Reference Sheets section to new card markup.

Verified​

CheckResult
Homepage latest card outputcategory + content type + title + updated + Read more
Tag permalink card outputsame markup
PHP lintno syntax errors

[2026-10-28] - Search filter UI refinement​

Refined the public-facing search placeholders after user feedback: the hero and palette now show Search docs... (filter by tag, e.g. tag:docker). Removed the visible hint line; all filter features (topic:, tag:, type:, :shorthand) remain available when typed. Public view advertises only the tag filter.

Changed​

  • Hero placeholder (GP elements 4090, 4316) and palette placeholder updated.
  • Removed server-rendered id86-search-note hint from the hero.
  • deploy-homepage.php updated for reproducibility.

Verified​

CheckResult
Origin hero placeholderSearch docs... (filter by tag, e.g. tag:docker)
REST filters still functionalyes

[2026-10-28] - Search filter by topic/category and tag​

Added conditional filtering to the Meilisearch-backed search on id86.net. The search box and REST API now accept filter tokens that narrow results by topic (category), tag, and/or content type, combined with AND.

Added​

  • Filter syntax in the search input (meilisearch-id86/assets/js/id86-meilisearch-global.js): explicit keys topic:/category:/cat:, tag:/tags:, type:/content_type:, plus shorthand :value (resolves across category, tags, and content type). Tokens are stripped from the search query and shown as active-filter chips above results.
  • REST params on /wp-json/id86/v1/search: category, tag (comma list), content_type, auto_filter (comma list). Empty query is allowed when filters are present; the response includes an filters object of applied filters.
  • Backend filter builder build_filter() in the meilisearch-id86 plugin (inc/class-meilisearch-client.php) constructs a safe Meilisearch filter expression (AND between dimensions, OR between multiple tags / shorthand), with quote and backslash escaping.
  • Server-side parsing of filter tokens embedded in q, so the REST API and UI behave consistently.
  • Palette placeholder updated to hint the filter syntax.

Changed​

  • REST proxy switched from GET to POST /search with a JSON body (q, limit, filter) to support complex filters.

Verified​

CheckResult
php -l functions.phpclean
node --check id86-meilisearch-global.jsclean
Origin-direct REST ?q=topic:code+gitGit Quick Reference
Origin-direct REST ?q=%3Acode2 Code docs
Origin-direct REST ?tag=dockerDocker Compose Essentials
Combined topic:code+tag:gitGit Quick Reference
deploy.sh to GC-US-M10 + OPcache flushsuccess

Notes​

  • Reuses the existing filterable attributes (category, content_type, tags); no reindex or Meilisearch settings change required.
  • Shorthand :code filters across category/tags/content type; explicit keys target a single dimension.
  • Filter logic lives in the meilisearch-id86 plugin (inc/class-meilisearch-client.php); the child theme no longer contains Meilisearch integration.

[2026-10-28] - Editing procedure documented, changelog folder renumbered​

Documentation and repository structure only. No change to the live site or to either snippet.

Added​

  • Editing the list in Design System → Technology Cards — the operational half of the tag allowlist, which was previously only described, not explained:
    • the exact file (wp-content/fluent-snippet-storage/5-id86-technology-cards.php, lines 39–56) and the WP admin route
    • the 69-slug / 18-slot rule and a swap / add / remove / reorder table
    • the six-per-row caution, so a swap does not silently shift every later tile
    • post-save purge commands (LiteSpeed origin-direct + Cloudflare) and the array_slice(id86_tech_tags(), 0, 18) verification one-liner
    • the backfill rule: the 18-slot cut happens after hide_empty, so an empty tag's slot fills itself from the next qualifying slug
  • Corrected the link shortcode attribute row, which still described the pre-revision truncation-only behaviour.

Changed​

  • id86.net/development/ → id86.net/10-development/, matching the numbered guide sections. Category label stays "10. Development Log", position 10.
  • Fixed the guide index in index.mdx, which still linked to ./development/changelog and would have 404'd after the rename.
  • 05-development/gp-elements.mdx now names id86_tech_tags() and its line range instead of saying "a snippet edit".

Verified​

CheckResult
Docusaurus build (build:id86.net, Node 22)[SUCCESS]
#editing-the-list anchor in built HTMLpresent
Nested purge / verify commandsrendered as highlighted code blocks, not literal text
Guide index link to section 10resolves after rename

[2026-10-27-revision] - Technologies band: 18 cards + /technologies/ index​

Same-day revision of the entry below. The band shipped at 12 cards with no exit, which measured badly against the corpus and left the index page unreachable.

Changed​

  • id86_tech_tags() expanded from 12 to 69 slugs, ordered so the first 18 form the homepage band — three semantic rows (languages, platform/data, infrastructure) — and the remainder is index-only.
  • Element 4414 content is now [id86_tech_cards limit="18" link="1"].
  • Shortcode gained limit="0" (render the whole allowlist), orderby="name", link / link_url / nav_label, plus a sibling [id86_tech_count].
  • The grid is wrapped in <nav aria-label> — 18 loose anchors in a div is not a landmark.
  • CSS snippet gained .id86-tech-nav and .id86-tech-more link styles.

Added​

  • Page 4416 /technologies/ — full-bleed hero plus [id86_tech_cards limit="0" min="1" link="0" nav_label="All technologies"].

Why 18​

CardsRows (desktop)Docs reachable from a visible chip
12268.6%
18374.5%
24480.0%
48888.0%

18 is the last step with a strong return. 48 was rejected on UX grounds: 8 rows on desktop, 24 rows on mobile, taller than the hero on a phone, and it flattens hierarchy so clippy renders identically to rust.

Gotcha​

The "View all" link was conditioned on truncation (count($all) > count($cards)). With only 8 technologies published the band is never truncated, so the link never rendered and /technologies/ was unreachable from anywhere. It now always renders when link="1", falling back to "Browse all technologies" without a number when nothing is truncated.

Verified​

CheckResult
Homepage cards8 rendered (all that qualify), limit="18"
Homepage linkBrowse all technologies → pointing at /technologies/
nav landmarkaria-label="Technologies" on home, "All technologies" on the index
/technologies/HTTP 200, exactly 1 <h1>, 8 cards, "8 technologies available"
Band orderhero → topics → technologies → latest → subscribe
Snippet PHPphp -l clean, error_files empty
LiteSpeed / Cloudflare200 / success: true for both URLs

[2026-10-27] - Homepage "Explore technologies" band​

A second browse axis on the homepage. Categories already answer which topic; tags answer which technology. The band sits directly under the topic cards and shows 12 small name-only tiles.

Added​

ArtifactLocationRole
GP Element 4414 ID86 Tech Cardsgp_elementsgenerate_after_header, priority 25, general:front_page
FluentSnippets PHP snippetwp-content/fluent-snippet-storage/5-id86-technology-cards.phpRegisters [id86_tech_cards] and holds the tag allowlist
FluentSnippets CSS snippetwp-content/fluent-snippet-storage/6-id86-technology-cards-css.phpCard grid styling, printed in wp_head
Deployer entryID86-instant-documentation/tools/deploy-homepage.phptech key added to $elements for reproducible rebuilds

How the list is controlled​

One function, one array, in the PHP snippet:

function id86_tech_tags() {
return apply_filters('id86_tech_tags', [
'rust', 'wordpress', 'php', 'python', 'docker', 'linux',
'git', 'bash', 'sql', 'cloudflare', 'nginx', 'tmux',
]);
}

Array order is display order. A slug that is not in the array cannot appear, so no exclude list is needed and junk tags (test, demo, Featured) are permanently out. A listed slug with no published posts is skipped automatically. Add, remove or reorder a technology by editing that array — no Element edit, no theme deploy.

Shortcode: [id86_tech_cards limit="12"], with optional min, min_cards, include, exclude, orderby. Full attribute table in Design System → Technology Cards.

Superseded by the revision entry above: the band now renders 18 cards with link="1", and the shortcode gained limit="0", orderby="name", link_url and nav_label.

Layout​

Hero Search 4090 priority 10
Niche Cards 4091 priority 20 Explore topics
Tech Cards 4414 priority 25 Explore technologies
Latest Sheets 4092 priority 30
Subscribe Bar 4128 priority 30 (front page)

Priority 25 was the only free slot; 10, 20 and 30 were already taken.

Snippet organization​

fluent-snippet-storage/ is a flat directory and must stay that way. CodeRunner::runSnippets() includes each published file by bare name from the auto-generated index.php, and filenames pass through sanitize_file_name(), which strips path separators. A snippet moved into a subfolder is never loaded.

FluentSnippets groups instead of folders. Every snippet carries a @group field, surfaced as the group filter in FluentSnippets → Snippets and returned by Snippet::getAllSnippetTagsGroups(). All six snippets were assigned one:

GroupSnippets
single-post1-hide-author-on-all.php, 2-cross-link-review-related-posts.php
admin3-content-type-metabox.php, 4-hide-betterlinks-metaboxes.php
homepage5-id86-technology-cards.php, 6-id86-technology-cards-css.php

@tags is the second axis (id86, homepage, css, …). Use groups for which area of the site and tags for what the snippet does.

Verified​

CheckResult
shortcode_exists('id86_tech_cards')true
Origin homepage HTML<section class="id86-section id86-tech-cards"> present, 5 cards rendered
Section order in outputhero → niche-cards → tech-cards → latest → subscribe-bar
Card CSS in <head>1 snippet <style> block, rules intact
Snippet registry6 snippets published, error_files empty
LiteSpeed purge (origin-direct)HTTP 200
Cloudflare purge (homepage URL)success: true

Only five technologies currently qualify — python, docker, linux, git, tmux — because the site has 19 posts and the 10,614-file Markdown corpus has not been imported yet. The band will fill to 12 as the sync runs. Set min_cards="6" on the Element before public launch so a three-tile row never ships.

Gotchas worth remembering​

  • FluentSnippets dispatches CSS on a lowercase type string. CodeRunner::runSnippets() uses case 'PHP': … case 'js': … case 'css':. A CSS snippet stored with type CSS falls through to default, prints nothing, and logs no error. The CSS snippet in this change was created as CSS, produced no output, and had to be re-saved as css. PHP snippets correctly store PHP uppercase — the two conventions genuinely differ.
  • The homepage is behind Cloudflare Access. A plain curl https://id86.net/ returns 302 to rezriz.cloudflareaccess.com, so front-end verification must go through the origin: curl --resolve id86.net:443:127.0.0.1 https://id86.net/.
  • gp-elements.mdx previously documented every homepage element at priority 10. They were actually 10 / 20 / 30. Corrected in the same change.
  • Shortcodes in gp_elements hook blocks need no extra meta. Element 4092 has rendered [id86_latest_sheets] for months with no _generate_hook_execute_shortcodes key.

Documentation updated​

  • 02-design-system/topic-and-reference-cards.mdx — new "Technology Cards" section
  • 02-design-system/css-system.mdx — snippet CSS layer, inventory row, dispatch gotcha
  • 05-development/gp-elements.mdx — element 4414, corrected priorities, shortcode layer split

Rollback​

# Element
wp post delete 4414 --force

# Snippets: delete both files through FluentSnippets → Snippets,
# or restore the pre-change snapshot:
tar xzf ~/backups/id86-snippets-<timestamp>.tar.gz -C wp-content/

The pre-change snapshot is ~/backups/id86-snippets-20261027-151235.tar.gz on GC-US-M10. Restoring it removes both new snippets and reverts the grouping applied to the four existing ones.