Full-stack Documentation Push

Current as of 2026-08-26 -- maintained_current -- v6 development closeout and local website reconciliation. DOCFLUSH-20260825-001 is closed in the development tree and review-needed. E0-E7 are proven; E8 remains the distinct owner gate for manual acceptance, source staging, and website publication. No public mutation is claimed. Earlier runs remain preserved below with their original event dates.

Why this vertical exists

The documentation system derives from source behavior, source comments, usage contracts, and file metadata. A major messaging and runtime change therefore requires a governed reharvest: not because every small change deserves a full publication run, but because this change crossed enough source, HELP, manual, and public-documentation boundaries to justify the complete vertical.

The chain is:

source and *ref.hpp contracts
-> COMMENTS SRC* evidence and mutation audit
-> CMDHELP build + CMDHELPCHK + locale canaries
-> SelfDoc / reference identity / lineage
-> manualgen candidate + accepted-layer preservation
-> assembled Markdown, HTML, and PDF
-> reviewed website pages and machine-readable feeds
-> human review
-> explicit commit, publication, and live-readback gates

Current proof table

2026-07-28 update — manualgen command-reference lane advanced. Past this 07-23 snapshot, a manualgen gate-4 apply (MANRUN-20260728T041930Z-5DE4733C, harvest HELPMETA-20260728T003402Z) accepted the five FoxPro string functions STUFF, PADL, PADR, PADC, and PROPER into the dev-tree command reference: 164 reader-linked pages, 10,502 lineage rows, SYSCMD 212 / SYSFUNC 74, publication-readiness PASS. This is a distinct manualgen assembly from the 191-page candidate above (do not compare page counts), and it is not source-promoted or deployed. See the Command Reference manualgen lane.

Coverage repairs made during review

The first local website candidate was too scant. A source-to-reference reconciliation found and repaired eight post-baseline command pages: BUILDVECTORS, DEFCMD, DEFFN, STOP_ON_ERROR, UNDEFCMD, UNDEFFN, USER, and VDISK. The current-source blocking count is zero; 102 inherited historical gaps remain visible as backlog rather than being relabeled as new regressions.

Two large implementation families also received dedicated documentation:

• RAM DBF and VDISK: process-local X64 DBF tables, CDX-V64 indexes, path routing, and destructive lifetime boundaries.
• Identity, Authentication, and RBAC: USERS identity records, TEAM_MEMBER participation, authentication sessions, roles, permissions, authorization grants, DBF persistence, owner-gated management, runtime enforcement, and the diagnostic-only legacy SECURITY selector.

Human-viewable products

• Current Tasks & Projects — what is active, owner, evidence state, Pseudo-Chat inbox, and next gate.
• Documentation Progress — published checkpoint plus current vertical without conflating their dates.
• Developer Manual — assembled current manual.
• Command Reference — accepted and current page layers with lineage.
• Website Documentation Matrix — content maintenance classes, feed authorities, and proof gates.
• Pinocchio Benchmarks — historical before/after evidence and machine identity limitations.

Machine-readable companions:

• current-work-v1.json
• documentation-progress-v1.json

Date and maintenance contract

This page, Current Tasks & Projects, Documentation Progress, project truth, roadmap, manual landing, and AI Agent Sync are permanent but not static. They use the maintained_current class:

1. Display a reconciled as_of_date.
2. Name the authority that feeds the present state.
3. Show proof state and next gate.
4. Replace the present-state region when work advances.
5. Preserve historical event dates and immutable closeout evidence.

Reported products such as benchmark rows and sealed publication checkpoints remain append-only. Static brand/history pages change only by deliberate human review.

Additional maintained steps (added in pass 4)

Pass 4 added standing steps to the vertical; Document FullStack push v5 runs them by default:

1. Website matrix gate. Read and classify against the Website Documentation Matrix at the start of the website phase; update and re-audit it at closeout. A stale matrix is a fail-closed condition on the website signoff.
2. Conceptual diagram collection. The BBS/AI process diagrams and the start-to-finish documentation-push DFD are maintained from source .mmd; regenerate the SVGs from source and never hand-edit a rendered SVG.
3. AutoSSL trigger. When the certificate validates, flip the artifact/manual-room links to HTTPS and drop the "while SSL is settling" caveats.
4. Count reconciliation (AIF-032). Reconcile the command count in source and regenerate the data-carrying harvest diagram and command catalog; do not hand-type harvest-derived numbers.
5. Interchange coverage. New import/export surfaces (such as AUTODBF, CSV-to-DBF) land in the DotScript CSV/DBF import-export section with a proof label.

Separate missions and open boundaries

• METACOLLECT-238 is a separate 238-finding metadata mission. It was not silently folded into this documentation flush.
• The Pseudo-Chat palette-stub return is held for correction and is not implemented.
• A local green website does not equal a commit, GitHub push, saved deployment, production deployment, or public live-readback.
• The next gate is human inspection of the complete local website followed by an explicit publication decision.