46c62ebefa
Three controller changes in one commit (tight code coupling): 1. /fp/tablet/request_reset_code (Task 2) — generates 4-digit code, emails it, returns masked_email. Specific error codes for the frontend to switch on (no_email + manager_name, rate_limited + wait_minutes, user_not_found, no_role, inactive). Shop-branch role check matches existing _check_credentials per Rule 13l + 23 (all_group_ids transitive — Owners reach Technician through implication). 2. /fp/tablet/verify_reset_code (Task 3) — verifies the emailed code, on success mints a 5-min HMAC reset_token. Error responses are specific (no_active_code / expired / too_many_attempts / wrong_code with attempts_left). 3. set_pin extended to accept reset_token (Task 4) — three auth paths now: old_pin (existing), reset_token (new), or neither (existing — only for users with no current hash). reset_token path is the only one that operates on a user OTHER than env.user; token proves the legit user just verified their email. Failure audit reuses existing failed_unlock event_type with a notes field describing the reset-code-specific reason. Success audit uses the new pin_reset_requested / pin_reset_code_verified / pin_set_after_reset event_type values. _mask_email helper added for the no-email-on-file edge case. 3 more tests cover: valid token roundtrip + set_pin, expired token rejection, and lockout-cleared-on-reset. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Fusion Plating — Shop Floor
Tablet / operator ergonomics layer for the fusion_plating core.
Part of the Fusion Plating product family by Nexa Systems Inc. Copyright (c) 2026 Nexa Systems Inc. All rights reserved. Licensed under OPL-1 (Odoo Proprietary License v1.0).
What this module adds
| Feature | Model |
|---|---|
| Tablet station registration | fusion.plating.shopfloor.station |
| Bake oven master + chart recorder ref | fusion.plating.bake.oven |
| Hydrogen embrittlement bake-window enforcer | fusion.plating.bake.window |
| First-piece inspection gate | fusion.plating.first.piece.gate |
| Operator next-up queue (transient) | fusion.plating.operator.queue |
Bake-window enforcer
When a high-strength-steel part exits the plating tank, a clock starts. Customer specification dictates the window (typically 1-4 hours) inside which the relief bake must begin. Missing the window requires scrap or rework — there is no retroactive fix.
The module models this as a first-class entity with:
plate_exit_time— clock startwindow_hours— customer specbake_required_by— computed deadlinestate—awaiting_bake -> bake_in_progress -> baked, withmissed_window/scrappedexit paths- A 5-minute cron that flips records past their deadline to
missed_windowautomatically - A kanban board grouped by state with theme-aware status colours
Tablet client
A backend OWL component (Odoo 19 conventions) registered as the
fp_shopfloor_tablet client action. It hosts:
- QR scan input (wedge scanner or on-screen keyboard friendly)
- Live tank / bath / job preview cards
- One-tap Start Bake / End Bake buttons
- Live operator next-up queue
JSON-RPC endpoints (Odoo 19 type='jsonrpc'):
POST /fp/shopfloor/scanPOST /fp/shopfloor/log_chemistryPOST /fp/shopfloor/start_bakePOST /fp/shopfloor/end_bakePOST /fp/shopfloor/queue
QR code conventions
| Prefix | Resolves to |
|---|---|
FP-TANK:<code> |
fusion.plating.tank |
FP-BATH:<name> |
fusion.plating.bath |
FP-STATION:<code> |
fusion.plating.shopfloor.station |
FP-JOB:<name> |
fusion.plating.bake.window |
FP-OVEN:<code> |
fusion.plating.bake.oven |
Security
Reuses the four core Fusion Plating groups (operator, supervisor, manager,
admin) defined in fusion_plating. No new groups, no new privilege block.
ACLs are graded operator (read/write logs), supervisor (create), manager
(full).
Theme
All styling is theme-aware: CSS custom properties + color-mix() against
Bootstrap / Odoo tokens. No hex codes, no media queries — works in light
and dark mode out of the box.
Install / update
docker exec odoo-dev-app odoo -d fusion-dev -u fusion_plating_shopfloor --stop-after-init