ELECTORAL COMMISSION — DATA COLLECTIONS SETUP
================================================

This phase adds a separate Electoral Commission Data Collections workspace
inside SLPS. It deliberately reuses the existing Data Collections builder,
response viewer, summaries, charts, spreadsheet-style response tools,
draft recovery, publishing, cover images and public collection forms.

The Electoral Commission workspace is isolated from the main Data Collections
workspace. Existing main collections remain in the 'main' scope; new Electoral
Commission collections are stored in the 'electoral' scope. The same signed-in
staff/administrator account can manage both areas, but their collections and
responses do not mix.

INSTALLATION
1. Back up the current SLPS project and database.
2. Upload the patch files into the existing slps directory, preserving folders.
3. In phpMyAdmin, select the existing SLPS database.
4. Import database/migrations/20261102_electoral_data_collections_scope.sql.
5. Log in as staff or administrator.
6. Open Electoral Commission from the SLPS sidebar.
7. Create a test collection, add questions, save draft, publish, submit a test
   response and review it under Responses. Confirm the main Data Collections
   workspace does not show the Electoral Commission test collection.

The public response form for an Electoral Commission collection is still a
Data Collections response form. It is not an election ballot and must not be
used for voting. The next phase will build the supervised, in-room voting
station workflow: staff-controlled voter check-in/authorisation, candidate
selection on the station computer, one ballot per authorised student, and
election result reporting. Students will not vote remotely through a link.

FILES ADDED
- shared/api/electoral_data_collections.php
- shared/views/modules/electoral-data-collections.php
- shared/views/electoral_data_collections_workspace.php
- database/migrations/20261102_electoral_data_collections_scope.sql

FILES MODIFIED
- shared/lib/data_collections.php
- shared/api/data_collections.php
- shared/api/collection_response.php
- shared/views/collect.php
- shared/js/data-collections.js
- shared/js/collection-response.js
- shared/views/module_shell.php
- shared/lib/panel_permissions.php
- shared/js/portal.js

VALIDATION
PHP and JavaScript syntax checks should be run before deployment. Test the
migration and workflows in staging before production use.
