Phase 6 originally scoped the full operator UI rewrite (Plant Overview, Tablet, Manager Dashboard, Process Tree). Tailscale SSH to entech is currently unavailable, so live in-browser verification of OWL/JS components isn't possible. Shipping a lean Phase 6 with the data-layer pieces: 1. /fp/job/<id> scan controller — when a user scans a fp.job sticker, lands them on the fp.job form (or the process tree action once that's wired). Mirrors fusion_plating_reports' /fp/wo/ pattern. 2. /fp/jobs/process_tree JSON endpoint — returns the recipe tree serialized with each node tagged by its fp.job.step state, ready for an OWL component to render. The component itself is deferred (see README.md). The bigger UI deferrals (kanban, tablet, manager dashboard) are documented in README.md. They get their own focused project after cutover — the data layer is complete, so they can land incrementally without touching fp.job/fp.job.step. Tests verify controller imports + serialization shape (no HTTP because TransactionCase doesn't easily simulate request context). Manifest 19.0.1.8.0 → 19.0.1.9.0. Part of: native job model migration (spec 2026-04-25) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
5 lines
92 B
Python
5 lines
92 B
Python
# -*- coding: utf-8 -*-
|
|
from . import models
|
|
from . import report
|
|
from . import controllers
|