GLMCHAT V2.2.1 — DOCUMENTATION COMPLIANCE AUDIT
Audit date: 22 July 2026
Scope: GLMCHAT_V2.2.1_ENVIRONMENT_CONTINUED_22072026164117.zip

AUDIT VERDICT
NO-GO FOR PRODUCTION.
CONDITIONAL STAGING CANDIDATE ONLY.

The deployable package is structurally consistent and the documented core feature surface is substantially represented in the shipped frontend and PHP backend. However, production approval is not supportable because the bundle's own controlling documents list sixteen open P0 acceptance gates, and those gates remain unevidenced.

BASELINE
- Audited the extracted handover and exact app/ deploy tree.
- No application source, runtime configuration, schema, migration, manifest, service worker, storage or user data was modified during this audit.
- The deployable application contains 81 files in DEPLOYMENT_MANIFEST.json; the package validator completed 281 structural checks.

DOCUMENT-TO-IMPLEMENTATION RESULTS

1. Architecture — PARTIALLY COMPLIANT
Passed:
- Flat PHP 8.2+ shared-hosting deployment layout is present.
- SQLite database, WAL/foreign-key configuration and 13 forward migrations are present.
- Deployment-relative PWA manifest, service worker and precache inventory are present.
- No Node, Python, Composer or container runtime is required by the deploy tree.
Open/material discrepancy:
- documentation/reference/FEATURE_AND_FUNCTION_MAP.txt describes maintainable React source, build scripts, feature-lock files and automated test suites as authoritative implementation assets, but those assets are absent from this release.
- app/README.md correctly discloses that the matching source repository and test suites are not included. The documentation set is therefore internally inconsistent and source-level claims cannot be reproduced.

2. Authentication and security — STATICALLY COMPLIANT; LIVE ACCEPTANCE OPEN
Verified in code/configuration:
- Six-digit PIN setup/login, CSRF, session handling, lockout and recent-PIN checks.
- Encrypted provider credentials and encrypted offline records.
- Same-origin CSP without unsafe-eval, private-path denial rules, HTTPS enforcement, HSTS and no-store API/shell handling.
- Destructive tool actions and sensitive interventions require recent reauthentication.
Not proven:
- Target LiteSpeed rewrite/header behaviour, HTTPS/proxy cookies, lockout under live concurrency and real-host private-path denial.

3. Chat, vision, reasoning and voice — IMPLEMENTED CONTRACTS; PROVIDER TESTS OPEN
Verified statically:
- Chat endpoint, SSE workflow execution, selected project/file context, image routing, reasoning controls, structured output, cost preflight, cancellation-related controls and TTS endpoints are represented.
- Frontend exposes vision, structured JSON output and voice controls.
Not proven:
- Live GLM-5.2 text/reasoning/streaming/cancellation.
- Live separate vision-model routing.
- Live function calling/tool continuation.
- Live Together TTS voices and playback.

4. Projects, library and agentic workflows — SUBSTANTIALLY COMPLIANT
Verified statically:
- Project CRUD/upload/file paths, metadata and linked automation surfaces.
- Agent, team and workflow definition APIs and frontend wizards.
- Immutable workflow snapshot/migration structures.
- Pause, resume, cancel, approval decisions and intervention routes.
- Worker reassignment, optional-stage skip, tool revocation and branch-checkpoint controls are represented in the UI/backend.
- Prompt and template CRUD/library surfaces are represented.
Not proven:
- Long-running execution, lease recovery, contention, interrupted uploads and large/hostile ZIP behaviour on the target host.

5. Offline, synchronisation and PWA — STATICALLY COMPLIANT; DEVICE ACCEPTANCE OPEN
Verified statically:
- Shell-only cache policy and API exclusion before cache handling.
- Controlled service-worker update messaging.
- AES-GCM local encryption, bounded offline credential age, ordered queue/conflict/auth-pause concepts.
- Relative start_url and scope, standalone display and valid icon dimensions.
Not proven:
- Physical Android install, offline restart, queued replay, browser eviction, quota pressure, Samsung Internet, Chrome, captive portal and low-connectivity behaviour.

6. Accessibility and Android UX — IMPLEMENTATION EVIDENCE PRESENT; PHYSICAL TESTS OPEN
Verified statically:
- Mobile-oriented CSS/assets, reduced-motion, focus/Android-back support and specialist navigation labels are present.
Not proven:
- TalkBack, 200% text, 320–600 CSS-pixel layouts, short landscape, keyboard focus lifecycle and download/storage behaviour on physical devices.

7. Data integrity and upgrades — MIGRATION STATIC CHECKS PASS; REAL DATA TESTS OPEN
Verified:
- 13 migrations apply to a fresh SQLite database.
- Reapplying the latest migration succeeds.
- A synthetic 12-to-13 upgrade retains integrity and foreign keys.
Not proven:
- Upgrade against cloned real production storage.
- Deliberately failed upgrade and rollback.
- Real user-data preservation under target-host failure modes.

VALIDATION EXECUTED
- Package validator: Passed — 281 structural checks.
- PHP CLI availability: Passed — PHP 8.4.16.
- Required PHP extensions:
  - json: Passed
  - openssl: Passed
  - fileinfo: Passed
  - sqlite3: Failed/missing
  - curl: Failed/missing
  - mbstring: Failed/missing
  - zip: Failed/missing
- Manifest/SBOM inventory checks: Passed.
- Fresh and synthetic upgrade migration checks: Passed.
- Live LiteSpeed, Together, Android and TalkBack checks: Not run; required external systems/devices are unavailable.

DOCUMENTATION DISCREPANCIES
D1 — MATERIAL: The authoritative feature map points to source, tests and build files not included in the handover, while the app README states they are unavailable. Production claims must use the README/current-status limitation until a matching source release is supplied.
D2 — LOW: Home-tile wording differs from the product README while preserving the same functions: “Run automation”, “Agent team”, “Automation Templates” and “Tool Permissions” replace some documented labels.
D3 — LOW: The package validator requires the app deploy root as its positional argument, but this invocation contract is not stated in the handover start instructions. Passing the handover root produces a misleading missing-.htaccess failure.

OPEN PRODUCTION BLOCKERS
The following remain open and are release-blocking:
- Complete PHP runtime with sqlite3, curl, mbstring and zip.
- LiteSpeed root and nested-path deployment.
- Live rewrite, headers, HTTPS/proxy and cookie checks.
- Real-storage upgrade and rollback.
- Live Together key, text, vision, function/tool and TTS paths.
- Streaming through production proxy/LiteSpeed.
- Workflow concurrency, leases and SQLite contention.
- Storage quota/IndexedDB failure and eviction.
- Large upload/ZIP interruption testing.
- Physical Android Chrome, Samsung Internet and TalkBack acceptance.
- Matching source build, type-check, lint and automated-suite reproduction.
- Formal decisions on React 16 risk and six-digit-PIN/offline threat model.

RECOMMENDED DISPOSITION
Do not deploy as production-approved. Deploy only to a non-production LiteSpeed staging location, complete every P0 gate with retained evidence, then repeat this documentation-compliance audit using the matching full source release.