📝 checkpoint-standards-section.md

STANDARDS (pinned — always included, never filtered out of shared context)

These apply to every contributor: Cl1-, Cl2-, OA-, Ge-, Gr-. Andrew (Architect & QA Lead) has final say and reviews all output before it's accepted into any file.

1. Doc-block — mandatory on every module, no exceptions

Every source file gets this exact header, filled in, at the top:

/**
* ========================================================
* Module: <Filename>
*
* @version <X.Y>
* @date <YYYY-MM-DD>
*
* Another collaboration between Andrew.human and Claude.ai
* ========================================================
*

Rule of thumb: if you touched the file, bump @version and @date. This exists because of the view_attach.php saga — "same error" repeatedly turned out to be ambiguity about which version was actually deployed. A script with no visible page output still self-reports its version somewhere (a die()/error message, a response header) — this isn't optional for "quiet" scripts.

2. Visible version banner — mandatory in rendered output

Not just the source doc-block — the module's actual live output (page render, log line, response header) must show the same version + date, clearly visible, not faint/muted styling.

3. Incremental only — never wholesale rebuild

For CollabCore and any shared/dependency package: add, delete, or replace individual files. Never regenerate the whole package for a single change.

4. Requisite/third-party mods — never modify directly

(e.g. WhoDownloadedAttachment, CustomSearch, Board-Icons-and-colours). Depend on them as-is. A real gap found in one gets flagged to Andrew for possible upstream reporting — it does not get patched locally.

5. Pre-flight acknowledgment

Before handing back code that touches a file, state explicitly:

If any answer is "no" where it should be "yes," say so — don't omit the line.