LLMWikis Test Plan

This file tells AIs how to verify LlmWikis changes without turning every content or handoff edit into a package release.

Metadata

Field	Value
Source site	llmwikis.org
Source URL	https://llmwikis.org/
Canonical AIWikis URL	https://aiwikis.org/llmwikis/files/uai-test-plan-uai-3ee3abfd/
Source reference	.uai/test-plan.uai
File type	uai
Content category	uai-system
Last fetched	2026-06-22T01:56:21.9510185Z
Last changed	2026-06-13T22:24:46.1363889Z
Content hash	sha256:3ee3abfd1c118565affe58e62baf7c7a23b8ab129982926de35a140b0ede08d0
Import status	unchanged
Raw source layer	data/sources/llmwikis/uai-test-plan-uai-3ee3abfd1c11.uai
Normalized source layer	data/normalized/llmwikis/uai-test-plan-uai-3ee3abfd1c11.txt

Current File Content

Review Boundary

Long-run agent and Agent-Staged Page language in the bounded preview is retained as source-file evidence only. Any promoted staged synthesis requires source traces and owner review before it can become canonical public guidance.

Structure Preview

• LlmWikis Test Plan
• Purpose
• Default Rule
• Targeted Check Selection
• Full Sweep Triggers
• Full Release Path
• Full Build Documentation Hygiene
• First And Final Response
• 2026-06-13 Full .uai And Wiki Wizard Dogfood Alignment Checks
• 2026-06-13 Desktop Sticky Header Checks
• 2026-06-13 Long-Run Agent Wiki Checks
• 2026-06-13 UAIX And LLMWikis Quality Sweep Checks
• 2026-06-13 Workspace v3.106.0 Package Checks

Raw Version

This public page shows a bounded preview of a large source file. The complete source remains in the raw and normalized source layers named in metadata, with the SHA-256 hash above for verification.

• Source characters: 12510
• Preview characters: 11993

Local absolute paths are redacted in this public view. The source hash and source-side raw layer are based on the unredacted source file.

---
uaix: "1.0"
type: custom
title: "LlmWikis Test Plan"
created: "2026-04-28"
updated: "2026-06-13"
author: "LlmWikis maintainers"
version: 6
---

# LlmWikis Test Plan

## Purpose

This file tells AIs how to verify LlmWikis changes without turning every content or handoff edit into a package release.

## Default Rule

For normal prompt-driven work, run the smallest meaningful set of checks tied to the files, routes, records, or behaviors changed. Do not build ZIPs, refresh `[local path redacted]`, or run full package/runtime smoke checks unless the task is release scoped, package scoped, explicitly asks for that level of verification, or changes global public behavior that needs broad confirmation.

## Targeted Check Selection

- Always consider `git diff --check` after edits.
- Run `scripts/Invoke-UaiFileIntake.ps1` before broad work, and rerun it when active intake files are moved or dispositioned.
- For edited PHP, run `studio wp eval-file scripts/lint-llmwikis.php` when the corrected Studio site is available; if the Studio registration blocker remains, report that blocker instead of claiming runtime lint passed.
- For setup wizard logic changes, run `npm run test:unit` for the browser/CommonJS core module and `npm run test:e2e` or `npm test` for the Playwright wizard fixture when Playwright browsers are available.
- For setup wizard coding-standards or context-budget changes, verify the rendered form, readiness checklist, generated packet, visitor-AI digest, first actions, and structured setup model preserve `.uai/coding-standards.uai`, DRY, once-and-only-once, SOLID, automated testing, context-budget, large-file, duplicate-file, and generated-history policies.
- For edited root discovery files, check `llms.txt`, `robots.txt`, or `sitemap.xml` directly and verify private `AGENTS.md`, `readme.human`, `.uai/`, intake files, and package archives are not exposed.
- For public page copy or route changes, check the affected route, route metadata, and related sitemap or `llms.txt` entry when the runtime is available.
- For starter-template or bundle changes, run `php scripts/test-llmwikis-starter-bundle.php` when PHP CLI is available and `powershell -NoProfile -ExecutionPolicy Bypass -File scripts/Test-LlmWikisPublicSurface.ps1`; these checks guard canonical template definitions, bundle manifests, dynamic ZIP drift, public routes, discovery files, and private-file exclusions.
- For handoff-only changes, verify the load list, active intake state, whitespace, and public guidance that names the pattern. Confirm the complete intake outcome rule is present: safe relevant files must produce actual site/system work, hot-memory outcome, LLM Wiki/AIWikis preservation outcome when configured, durable summary/disposition, checks, blockers, and source-site removal or keep-active reason before source-site removal. Confirm memory-only distribution is called a failed handoff and source-site `Archive/` is not created when long memory is configured. Do not run package publishing just because handoff files changed.
- For multisite workspace guidance changes, verify that public copy and setup-wizard output require per-repository Git preflight before Sync, pull, merge, commit, or push, and that mutable WordPress Studio SQLite databases are treated as ignored local runtime artifacts rather than mergeable source files.
- For AIWikis multisite guidance changes, verify that setup-wizard output and public/spec copy require site-owned public memory under `https://aiwikis.org/{site}/...`, allow `/site/` for the directory and `/org/` for global organization/workspace material, and reject root mixed-memory routes such as `/files/`, `/concepts/`, `/reports/`, `/browse/`, and `/browser/`.
- For hot/cold memory reorganizations, verify the AIWikis transfer manifest exists, copied-file hashes match, active LlmWikis files are shorter and still complete, and public guidance keeps AIWikis as cold memory rather than source authority.
- For Long-Run Agent Wiki Strategy changes, verify `/guide/long-run-agent-wikis/`, `?mode=long-run-agent`, wizard model output, starter bundle files, preflight rules, `llms.txt`, and `sitemap.xml`. Public copy must include Context-Folded Agent Run, Folded Run State, Active Subgoal, Completed Subgoal Summary, State Review, Active Wiki Navigation, Agent-Staged Page, Process-Quality Checks, and Retrieval Budget Checks, while excluding source-report acronyms, external research/project names, optimizer/model/benchmark names, hardware/training/performance claims, hosted service claims, hidden-memory claims, public MCP/write API claims, autonomous publishing claims, certification, endorsement, and conformance claims.

## Full Sweep Triggers

Run the package and broad smoke path only when one of these is true:

- The human asks to build, refresh, publish, or validate release ZIPs.
- The task changes package contents, checksums, publish scripts, mirrored UAIX package handling, theme/plugin activation behavior, or upload-package boundaries.
- The task changes root discovery files, public sitemap coverage, `llms.txt`, route seeding, canonical routes, permanent `410` retirement behavior, or global metadata behavior in a way that affects the whole public surface.
- The task is a pre-production, release-candidate, deployment, migration, or broad public-readiness pass.
- A targeted check exposes a failure whose blast radius cannot be bounded without the full sweep.

## Full Release Path

When a full sweep is required, use `scripts/publish-llmwikis-packages.ps1`. That path owns the WordPress upload ZIPs, checksum refresh, mirrored UAIX dogfood package copy, and source/site archive outputs.

## Full Build Documentation Hygiene

A full build or release pass must also clean and update source documentation before the result is treated as current:

- Reconcile `AGENTS.md`, `readme.human`, loaded `.uai` files, strategy/progress/public-surface records, source-document disposition notes, and any active Markdown source files that describe the state being packaged.
- Move old build history or pre-slim snapshots to AIWikis cold memory before compacting hot handoff files.
- Refresh `.uai/intake-index.uai` and disposition active source files before publishing release evidence.
- Verify `llms.txt`, `robots.txt`, `sitemap.xml`, WordPress upload ZIPs, and source/site evidence boundaries do not expose private `AGENTS.md`, private `.uai` files, root `readme.human`, raw intake files, preserved evidence files, package archives, or retired private docs.
- Keep source docs source-only unless a specific page intentionally converts their guidance into public handbook copy.

## First And Final Response

Before broad edits, the AI should name the targeted checks it expects to run and say whether a full release sweep is out of scope. In the final response, report which checks ran, which release/package checks were intentionally not run, and any blocker that prevented a relevant targeted check.

## 2026-06-13 Full .uai And Wiki Wizard Dogfood Alignment Checks

- Passed: `[local path redacted] -l wp-content\themes\llmwikis-knowledge-theme\inc\setup-wizard.php`.
- Passed: `[local path redacted] -l scripts\lint-llmwikis.php`.
- Passed: static rendered-source marker scan for `must be crawl maps`, `not every report or file from every site`, `/{site}/files`, and `/org/ or wiki/global/`.
- Passed: static lint-source marker scan for rendered wizard crawl-map assertions.
- Passed: active `.uai` placeholder and required-record scan as part of the cross-workspace pass.
- Passed: `git diff --check` for LlmWikis with line-ending notices only.
- Blocked/skipped: `studio wp eval-file scripts/lint-llmwikis.php` because Studio reported this directory is not added to Studio.
- Not part of this source-only pass unless explicitly requested: package build, live upload, public route verification, or publish claim.

## 2026-06-13 Desktop Sticky Header Checks

- Passed: `powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\Test-LlmWikisPublicSurface.ps1`.
- Passed: `php -l .\wp-content\themes\llmwikis-knowledge-theme\inc\setup-wizard.php`.
- Passed: focused static assertion for ecosystem strip placement, desktop sticky rule, mobile static rule, and admin-bar offset.
- Passed: Playwright computed-style smoke check using the real header partial and stylesheet; desktop computed `position: sticky`, `top: 0px`, and mobile computed `position: static`.
- Passed: `git diff --check` with line-ending normalization warnings only.
- Blocked/skipped: live/local WordPress rendered-route verification because `studio site status` reports this directory is not added to Studio.
- Not run: package build, live upload, public route verification, or publish claim.

## 2026-06-13 Long-Run Agent Wiki Checks

- Required syntax checks after source edits: `node --check wp-content/themes/llmwikis-knowledge-theme/assets/js/setup-wizard-core.js`, `node --check wp-content/themes/llmwikis-knowledge-theme/assets/js/site.js`, `node --check wp-content/themes/llmwikis-knowledge-theme/assets/starter/llmwiki-preflight.js`, and PHP lint for touched theme PHP files.
- Required behavior checks: `npm run test:unit` and `powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\Test-LlmWikisPublicSurface.ps1`.
- Public-surface assertions must guard the long-run route, wizard `long-run-agent` mode, starter artifacts, preflight validator, discovery files, and the source-specific forbidden-label scan.
- Handoff checks: rerun `scripts/Invoke-UaiFileIntake.ps1` after source-site removal or keep-active recording, verify active Content/Improvement buckets are `.gitkeep`-only or otherwise fully dispositioned, scan `.uai` for invalid extensions, and run `git diff --check`.
- Rendered local route checks are useful only when this WordPress site is registered in Studio or another local URL is available. Live route/discovery checks require real upload/copy evidence first.

## 2026-06-13 UAIX And LLMWikis Quality Sweep Checks

- Passed: `powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\Invoke-UaiFileIntake.ps1` (`Indexed 0 intake file(s).`).
- Passed: `node --check wp-content/themes/llmwikis-knowledge-theme/assets/js/setup-wizard-core.js`.
- Passed: `node --check wp-content/themes/llmwikis-knowledge-theme/assets/js/site.js`.
- Passed: `node --check wp-content/themes/llmwikis-knowledge-theme/assets/starter/llmwiki-preflight.js`.
- Passed: PHP lint for `functions.php`, `inc/setup-wizard.php`, `inc/reference-pages.php`, `inc/starter-bundle.php`, `scripts/lint-llmwikis.php`, and `scripts/test-llmwikis-starter-bundle.php`.
- Passed: `npm run test:unit` (`12/12`) after adding scoped preflight coverage.
- Passed: `npm run test:e2e` (`30/30`).
- Passed: `powershell -NoProfile -ExecutionPolicy Bypass -File .\scripts\Test-LlmWikisPublicSurface.ps1`.
- Passed: `[local path redacted] scripts\test-llmwikis-starter-bundle.php`; byte-level ZIP inspection was skipped by that script because `ZipArchive` is unavailable.
- Passed: scoped preflight `node scripts/llmwiki-preflight.js validate --root . --wiki ..\AIWikis\wiki\llmwikis --sourceWiki ..\AIWikis\wiki\llmwikis --site llmwikis`.
- Passed: `git diff --check` with line-ending normalization warnings only.
- Live read-only probes: `https://llmwikis.org/`, `/tools/llm-wiki-setup-wizard/`, `/llms.txt`, and `/sitemap.xml` returned 200; `/guide/long-run-agent-wikis/` returned 404 because the route remains source-only and unpublished.
- Known remaining failure: unscoped preflight still reports broad AIWikis root-corpus debt outside the scoped LLMWikis surface; keep this separate from scoped LLMWikis readiness.

## 2026-06-13 Workspace v3.106.0 Package Checks

- Passed: workspace recovery sync for 21 sites at `v3.106.0`.
- Passed: full workspace package build: 248 deployable artifacts.
- Passed: deployment readiness `815/0/0`.

Why This File Exists

This is a UAI AI Memory handoff file from llmwikis.org. It is shown here because AIWikis.org is demonstrating the real source files that make the UAIX / LLM Wiki memory system work, not only summarizing those systems after the fact.

Role

This .uai file is a compact custom packet. It keeps one kind of durable project truth separate from the rest of the archive so an agent can load the topic it needs without pulling the whole project history into prompt context.

Structure

The file is structured around these visible headings: LlmWikis Test Plan; Purpose; Default Rule; Targeted Check Selection; Full Sweep Triggers; Full Release Path; Full Build Documentation Hygiene; First And Final Response. Those headings are retrieval anchors: a crawler or LLM can decide whether the file is relevant before reading every line.

Prompt-Size And Retrieval Benefit

Keeping this material in a separate file reduces prompt pressure because an agent can load this exact unit only when its role, source site, category, or hash is relevant. The surrounding index pages point to it, while this page preserves the full content for audit and exact recall.

How To Use It

• Humans should read the metadata first, then inspect the raw content when they need exact wording or provenance.
• LLMs and agents should use the source site, category, hash, headings, and related files to decide whether this file belongs in the active prompt.
• Crawlers should treat the AIWikis page as transparent evidence and follow the source URL/source reference for authority boundaries.
• Future maintainers should regenerate this page whenever the source hash changes, then review the explanation if the role or structure changed.

Update Requirements

When this source file changes, update the raw source layer, normalized source layer, hash history, this rendered page, generated explanation, source-file inventory, changed-files report, and any source-section index that links to it.

Related Pages

• Source overview
• Site file index
• Site report index
• UAI system index
• Source provenance
• Site directory
• Organization reports

Provenance And History

• Current observation: 2026-06-22T01:56:21.9510185Z
• Source origin: current-source-workspace
• Retrieval method: local-source-workspace
• Duplicate group: sfg-314 (primary)
• Historical hash records are stored in data/hashes/source-file-history.jsonl.

Machine-Readable Metadata

{
    "title":  "LLMWikis Test Plan",
    "source_site":  "llmwikis.org",
    "source_url":  "https://llmwikis.org/",
    "canonical_url":  "https://aiwikis.org/llmwikis/files/uai-test-plan-uai-3ee3abfd/",
    "source_reference":  ".uai/test-plan.uai",
    "file_type":  "uai",
    "content_category":  "uai-system",
    "content_hash":  "sha256:3ee3abfd1c118565affe58e62baf7c7a23b8ab129982926de35a140b0ede08d0",
    "last_fetched":  "2026-06-22T01:56:21.9510185Z",
    "last_changed":  "2026-06-13T22:24:46.1363889Z",
    "import_status":  "unchanged",
    "duplicate_group_id":  "sfg-314",
    "duplicate_role":  "primary",
    "related_files":  [

                      ],
    "generated_explanation":  true,
    "explanation_last_generated":  "2026-06-22T01:56:21.9510185Z"
}