LockerPad 2.1.0 — implementation boundaries

Page content is not encrypted. Direct file URLs are not protected. URL-path rules only
apply to requests handled by WordPress. Explicit selections set a WordPress password
fallback and preserve the previous password for restoration.

Visitor POST actions require HTTPS, exact same Origin, X-LockerPad: 1 and a WordPress
nonce. Anonymous WordPress nonces are not proof of identity. Unlock additionally checks
rate limits and unique credentials; session, extension and page delivery require a
valid per-lock session, current grant, current versions, expiry and revocation checks.
All administrative writes require manage_options and a WordPress nonce. Content search
also checks the administrator's ability to edit each page/post.

All frontend assets use enqueue APIs and load only at a page gate, unlocked protected
page (timer only) or admin preview. The protected-widget HTML/style endpoint is removed.

Existing schema columns for body/files/scripts are retained for lossless migration,
not used as premium functionality. Legacy media entries are excluded from unlocks;
there are no media endpoints. Legacy grants/files/keys are preserved. A mixed old vault
with explicitly assigned pages gets a separate page lock with the original hashes.
Uninstall preserves shared data when legacy media or Pro use is detected.

No network calls to ChatRep, no remote executable updates and no external services.
Run the standalone Pro edition separately; it is not currently an add-on to this build.

Passwords preserve exact Unicode, spaces and punctuation (1–100 code points). Control
characters and invalid UTF-8 are rejected. HMAC preprocessing covers the entire secret
before bcrypt, avoiding bcrypt's 72-byte truncation. Only salted verifiers and scoped
keyed lookups are saved. Blank edits retain a prior verifier. AND pairs must match the
same person's grant; ambiguous OR identities are rejected. Only the nine explicitly
listed single/paired modes are accepted, with no zero- or three-method configuration.

The 2.1 upgrade adds empty password verifier/index columns and expands mode storage,
without changing existing dial/seed hashes. The renamed path-cache transient expires
after five minutes; old lp_paths_ cache entries expire without migrating user settings.
