[ROADMAP] ServiceTag post-1.7 backlog and execution tracker

[GonzRon]

Purpose

This is the authoritative ServiceTag roadmap after the ServiceTag 1.7.0 release (now tracking from the 1.8.0 baseline).

It supersedes #76, whose historical roadmap spanned the 1.4 → 1.7 development period and accumulated obsolete release sequencing. Use this issue for current prioritization and dependency order. Closed historical issues remain the record of what shipped; they are not rewritten into the current roadmap.

Current released baseline: servicetag-v1.8.0, published 2026-10-05 (before it: servicetag-v1.7.0, 2026-10-04).

Released 2026-10-05 as ServiceTag 1.8.0: localization (#102), the former 1.7.1 maintenance content (#94 #99 #101 #103) and the former 1.7.2 Home Assistant setup UX (#105) — all shipped and closed. Owner ruling 2026-10-04: 1.7.1 and 1.7.2 are folded into 1.8.0; neither is released on its own. No next release train is promoted yet (tracker rule below); the sections after 1.8.0 are organised by capability.

Tracker rules

1. Do not put a release number in an open issue title unless that release is an active, owner-approved target. A passed target becomes stale metadata.
2. Use capability/status prefixes instead: [NEXT], [BUG], [MAINTENANCE], [FUTURE], [LATER], plus a domain such as [BLE], [TELEMETRY], [INTELLIGENCE], [LOCALIZATION].
3. Dependencies remain explicit even when release assignment is intentionally undecided.
4. A new release updates this baseline and this tracker; do not create another historical narrative inside every feature issue.
5. [DEFERRED][REFACTOR] Namespace/application identity reset to com.servicetagnfc.servicetag #98's namespace/application-identity reset is permanently deferred. It is not part of the current roadmap and must not be reintroduced as an implied release gate.

Shipped foundation now assumed

The current backlog may rely on these completed foundations without re-planning them:

• [PHASE 2][MVP][FOUNDATION] SupplyItem catalog, specs, applicability, and usage linkage #15 — canonical SupplyItem catalog/applicability/usage linkage
• [PHASE 2][MVP][FOUNDATION] Installed Components: fitted state and replacement history #47 — Installed Components fitted state/history
• [NEXT-2][AFTER #15 + #47][ENHANCEMENT] Attach resources and Share intake to components and supplies #69 — shared resources for Assets, SupplyItems and Installed Components
• [SHIPPED][FEATURE] Home Assistant operating-season synchronization #16 — Home Assistant operating-season synchronization
• ServiceTag 1.8.0 — current released application baseline (1.7.0 before it)
• Shipped in 1.8.0: [1.8.0][LOCALIZATION] Android localization foundation and language packs #102 localization foundation and nine language packs (Localize the Android app: string resources and nine language packs (#102) #106); the former 1.7.1 maintenance train ([1.7.1][BUG][API] Schedule POST/PATCH answers 500 on a body with a key and no value #94 [1.7.1][MAINTENANCE][TEST] TransferGraphRetainTest fixture coverage is vacuous for empty defaulted lists #99 [1.7.1][MAINTENANCE][DOCS] Correct stale security/privacy and README statements #101 [1.7.1][UI/UX] Maintenance tab and Settings cleanup; move Reminder health to Utilities #103, 4726a2b); [1.8.0][HOME ASSISTANT][UX] Browse and pick boolean entities during season-sync setup #105 the Home Assistant entity picker in the setup sheet (#105 Browse and pick a Home Assistant entity during season-sync setup #107)

ServiceTag 1.8.0 — released 2026-10-05

MINOR under docs/versioning.md: #102 adds new user-facing language/localization behaviour. It carries three streams:

stream	issues	state
Localization	#102	merged (#106, c994341)
former 1.7.1 maintenance train	#94, #99, #101, #103	merged (4726a2b); plan and rulings in docs/superpowers/plans/2026-10-04-servicetag-1.7.1/
former 1.7.2 Home Assistant setup UX	#105	merged and closed (#107, 29d5876; test follow-ups #108 and #110)

1.8.0 was cut on 2026-10-05 as servicetag-v1.8.0 on 50bc0328 (version 1.8.0 / code 21; Room schema 21 / backup format 20 unchanged), with the docs/versioning.md row and docs/releases/1.8.0.md for all three streams. The pre-cut connected suite (R2 on emulator-5554, which no CI job runs) found the instrumented sources uncompiled after #107 and 14 connected cases stale after #102 and #103 — fixed in #108 and #110 with no app change — and one lint error from #102, fixed in #109; CI now compiles the instrumented sources and runs lint. The release-tip proofs, the real-Home-Assistant picker proof and the 1.7.0 → 1.8.0 upgrade with the token-survival check are recorded in docs/architecture/product-split-evidence.md.

Notes for 1.8.0's release notes:

• one /v1 behaviour change a script could meet: a schedule command body with a key and no value is 400 where it was 500 ([1.7.1][BUG][API] Schedule POST/PATCH answers 500 on a body with a key and no value #94);
• the Maintenance tab's new layout and Reminder health under Settings › Utilities ([1.7.1][UI/UX] Maintenance tab and Settings cleanup; move Reminder health to Utilities #103);
• the localization programme is presentation-layer only: canonical domain/API/NFC values stay language-neutral; language packs are additive and do not depend on [DEFERRED][REFACTOR] Namespace/application identity reset to com.servicetagnfc.servicetag #98.

Former 1.7.1 — complete

#94 (schedule POST/PATCH 400 not 500), #99 (the vacuous TransferGraphRetainTest hole), #101 (documentation corrections), #103 (Maintenance tab / Settings cleanup, Reminder health placement and healthy state). All four closed. It was planned as a PATCH train and kept to that scope; by the ruling above it ships inside 1.8.0 rather than as 1.7.1.

#90 remains conditional test-suite architecture debt; promote only if its established timing/growth threshold requires it.

Former 1.7.2 — #105, complete

• [1.8.0][HOME ASSISTANT][UX] Browse and pick boolean entities during season-sync setup #105 — browse/search/select Home Assistant boolean entities during season-sync setup

It improves the shipped #16 setup flow but does not add new season semantics, a new integration type, or a new canonical domain capability: the stored binding remains the same exact Home Assistant entity ID; #105 adds discovery/search/picker UX around that existing contract. Planning begins now that #102 and the 1.7.1 train are both on master, so its user-visible strings are added as localized resources from the start.

ServiceTag 1.9.0 — intelligence / equipment research

Dependency shape:

#42 foundation/workflows → #75 focused equipment-label workflow, with broader #42 research/import work continuing as designed.

• [1.9.0][INTELLIGENCE] Pluggable LLM backends and structured equipment-research workflows #42 — provider-neutral LLM backends and structured equipment research
• [1.9.0][INTELLIGENCE] Extract Asset identity and specifications from equipment-label photos #75 — extract Asset identity/specifications from equipment-label photos

This is now the owner-approved 1.9.0 release train.

ServiceTag 2.0.0 — maintenance / materials expansion

Owner-assigned 2.0 train:

• [2.0.0][MAINTENANCE-MODEL] Preserve ranged and conditional manufacturer maintenance guidance #88 — preserve ranged and conditional manufacturer maintenance guidance
• [2.0.0][REPLACE-ASSET] Carry Supply applicability through Replace Asset review #97 — carry Supply applicability through Replace Asset review
• [2.0.0][SUPPLIES] SupplyItem inventory, low-stock, and reorder readiness #95 — SupplyItem inventory, low-stock and reorder readiness
• [2.0.0][COMPONENTS] Component maintenance requirements and stock-aware replacement orchestration #96 — component maintenance requirements and stock-aware replacement orchestration

Dependency/model rules:

• [PHASE 2][MVP][FOUNDATION] SupplyItem catalog, specs, applicability, and usage linkage #15 remains the one canonical SupplyItem identity.
• [PHASE 2][MVP][FOUNDATION] Installed Components: fitted state and replacement history #47 remains the fitted-component/current-state/history model.
• [2.0.0][SUPPLIES] SupplyItem inventory, low-stock, and reorder readiness #95 adds inventory/procurement readiness; it does not become ERP/accounting.
• [2.0.0][COMPONENTS] Component maintenance requirements and stock-aware replacement orchestration #96 adds maintenance-material and replacement orchestration rather than a second parts/component model.
• [2.0.0][MAINTENANCE-MODEL] Preserve ranged and conditional manufacturer maintenance guidance #88 preserves source guidance separately from the deterministic operational schedule.
• [2.0.0][REPLACE-ASSET] Carry Supply applicability through Replace Asset review #97 extends the existing reviewed Replace Asset carry-forward workflow.

Versioning classification: 2.0.0 is an explicit owner-declared product-generation boundary. docs/versioning.md now permits a backward-compatible MAJOR for a substantial expansion that establishes a new ServiceTag generation, while still requiring MAJOR for any breaking contract. Do not manufacture incompatibility to justify 2.0; preserve backward-compatible schemas, backups, APIs, NFC contracts and migrations wherever sound.

Telemetry / declarative BLE

Dependency order remains:

#56 → #57 → #59 → #58

• [FUTURE][TELEMETRY][FOUNDATION] Canonical telemetry source bindings and ingestion pipeline #56 — canonical telemetry source bindings and ingestion pipeline
• [FUTURE][BLE] Runtime-installable BLE Device Profiles and on-demand protocol engine #57 — runtime-installable BLE Device Profiles and on-demand protocol engine
• [FUTURE][BLE] Declarative GATT session codecs for read-only telemetry devices #59 — declarative GATT session codecs for read-only telemetry devices
• [FUTURE][BLE] Device Protocol Lab for capture, inspection, and profile authoring #58 — Device Protocol Lab for capture/inspection/profile authoring

These were formerly labelled as "1.7" work. They did not become complete merely because ServiceTag 1.7.0 shipped. They remain future work with the dependency order above and no current release assignment.

External-state integrations

• [FUTURE][ENHANCEMENT] Generic REST boolean-state source adapter #100 — generic REST boolean-state source adapter

#105 was promoted into the Home Assistant setup UX work now carried by 1.8.0. #100 remains a separate future provider-neutral REST adapter.

Later domain / workflow enhancements

• [LATER][UX] Surface contextual Asset actions after NFC scan #89 — contextual Asset actions after NFC scan
• [LATER] Reminder-fatigue controls per schedule #26 — reminder-fatigue controls per schedule
• [LATER] Merge a backup set into an existing ServiceTag database #44 — merge a backup set into an existing ServiceTag database
• [LATER] Pluggable attachment and backup replication providers #45 — pluggable attachment and backup replication providers

These stay intentionally unassigned to a release until promoted.

Long-running umbrella

• [EPIC] ServiceTag: the NFC-first maintenance tracker #1 — ServiceTag NFC-first maintenance tracker epic

#1 describes product direction and historical phase structure. This issue (#104) is the authority for current sequencing.

Test-suite promotion rule

#90 is not an automatic roadmap step. Continue measuring the ordinary merged-tip gate and promote #90 when the established timing threshold is exceeded, or when the next planned feature would predictably cross it.

Roadmap principle

Prefer stable capability dependencies over speculative release labels.

A future release train should be written here only when the owner actually promotes it; until then, open issues remain organized by capability and dependency rather than by a version number that may become obsolete.

---

Tracker body updated 2026-10-05 for the 1.7.1 → 1.8.0 fold; the 1.7.1 section's scope rule and the separate 1.7.2 section were replaced by the 1.8.0 section above. Updated again 2026-10-05 for the 1.8.0 release: baseline, the 1.8.0 section and #105 marked shipped.

[GonzRon]

Tracker reconciliation completed after the ServiceTag 1.7.0 release.

Changes made:

• [SUPERSEDED][ROADMAP] Historical 1.4–1.7 execution tracker #76 closed and marked superseded; [ROADMAP] ServiceTag post-1.7 backlog and execution tracker #104 is the new sequencing authority.
• [DEFERRED][REFACTOR] Namespace/application identity reset to com.servicetagnfc.servicetag #98 marked permanently deferred / not planned and removed as a release gate.
• [SHIPPED][FEATURE] Home Assistant operating-season synchronization #16 retitled as shipped rather than pre-1.0.
• stale release-target titles removed:
  • [1.9.0][INTELLIGENCE] Pluggable LLM backends and structured equipment-research workflows #42, [1.9.0][INTELLIGENCE] Extract Asset identity and specifications from equipment-label photos #75: 1.6 → FUTURE / INTELLIGENCE
  • [FUTURE][TELEMETRY][FOUNDATION] Canonical telemetry source bindings and ingestion pipeline #56, [FUTURE][BLE] Runtime-installable BLE Device Profiles and on-demand protocol engine #57, [FUTURE][BLE] Device Protocol Lab for capture, inspection, and profile authoring #58, [FUTURE][BLE] Declarative GATT session codecs for read-only telemetry devices #59: 1.7 → FUTURE / TELEMETRY-BLE
• [FUTURE][TELEMETRY][FOUNDATION] Canonical telemetry source bindings and ingestion pipeline #56 → [FUTURE][BLE] Runtime-installable BLE Device Profiles and on-demand protocol engine #57 → [FUTURE][BLE] Declarative GATT session codecs for read-only telemetry devices #59 → [FUTURE][BLE] Device Protocol Lab for capture, inspection, and profile authoring #58 dependency order preserved without assigning a release.
• maintenance/bug titles normalized on [MAINTENANCE][TEST] Keep the device suite thin: classify, move tests down, budgets; merged-tip gate within 15 minutes #90, [1.7.1][BUG][API] Schedule POST/PATCH answers 500 on a body with a key and no value #94, [1.7.1][MAINTENANCE][TEST] TransferGraphRetainTest fixture coverage is vacuous for empty defaulted lists #99, [1.7.1][MAINTENANCE][DOCS] Correct stale security/privacy and README statements #101.
• [1.8.0][LOCALIZATION] Android localization foundation and language packs #102 normalized as FUTURE / LOCALIZATION.
• [1.7.1][UI/UX] Maintenance tab and Settings cleanup; move Reminder health to Utilities #103 identified as the current NEXT UI/UX cleanup.
• surviving open references that used [SUPERSEDED][ROADMAP] Historical 1.4–1.7 execution tracker #76 as coordinator were repointed to [ROADMAP] ServiceTag post-1.7 backlog and execution tracker #104.
• [EPIC] ServiceTag: the NFC-first maintenance tracker #1 now explicitly says [ROADMAP] ServiceTag post-1.7 backlog and execution tracker #104 owns current sequencing; its older phase narrative is historical context.

Open issues are now organized by capability/status rather than expired release labels.

[GonzRon]

Release assignment — 2026-10-04

ServiceTag 1.7.1 is the first maintenance release after 1.7.0:

• [1.7.1][BUG][API] Schedule POST/PATCH answers 500 on a body with a key and no value #94
• [1.7.1][MAINTENANCE][TEST] TransferGraphRetainTest fixture coverage is vacuous for empty defaulted lists #99
• [1.7.1][MAINTENANCE][DOCS] Correct stale security/privacy and README statements #101
• [1.7.1][UI/UX] Maintenance tab and Settings cleanup; move Reminder health to Utilities #103

ServiceTag 1.8.0 is the localization release anchored by #102.

Reason: docs/versioning.md classifies bug fixes, small UI corrections, security/reliability fixes as PATCH, but a new user-facing capability as MINOR. Shipping new languages is therefore 1.8.0 rather than 1.7.2.

[GonzRon]

Release assignments — 2026-10-04

• ServiceTag 1.9.0: [1.9.0][INTELLIGENCE] Pluggable LLM backends and structured equipment-research workflows #42 → [1.9.0][INTELLIGENCE] Extract Asset identity and specifications from equipment-label photos #75 intelligence / equipment-research train.
• ServiceTag 2.0.0: [2.0.0][MAINTENANCE-MODEL] Preserve ranged and conditional manufacturer maintenance guidance #88, [2.0.0][REPLACE-ASSET] Carry Supply applicability through Replace Asset review #97, [2.0.0][SUPPLIES] SupplyItem inventory, low-stock, and reorder readiness #95, [2.0.0][COMPONENTS] Component maintenance requirements and stock-aware replacement orchestration #96 maintenance/materials expansion.

2.0.0 is an intentional product-generation MAJOR. docs/versioning.md has been amended accordingly: breaking compatibility always requires a MAJOR, but a MAJOR does not require breaking compatibility when the owner explicitly declares a substantial expansion as a new ServiceTag generation.

For this train, #88/#97/#95/#96 materially broaden ServiceTag's canonical maintenance/materials model, so 2.0.0 is the declared generation boundary. This is not permission to manufacture a breaking change; backward-compatible schemas, backups, APIs, NFC contracts and migrations should be preserved wherever they remain sound.

[GonzRon]

Release assignment — 2026-10-04

ServiceTag 1.7.2

• [1.8.0][HOME ASSISTANT][UX] Browse and pick boolean entities during season-sync setup #105 — Home Assistant entity/device browser and boolean-entity picker for season-sync setup.

Classified as PATCH because it improves the existing #16 setup workflow without changing season semantics, binding identity, or introducing a new integration type.

[GonzRon]

1.7.1 — complete, folded into 1.8.0 (owner ruling 2026-10-04)

• [1.7.1][BUG][API] Schedule POST/PATCH answers 500 on a body with a key and no value #94, [1.7.1][MAINTENANCE][TEST] TransferGraphRetainTest fixture coverage is vacuous for empty defaulted lists #99, [1.7.1][UI/UX] Maintenance tab and Settings cleanup; move Reminder health to Utilities #103 closed; merged into master by 4726a2b and carried by c994341 (the [1.8.0][LOCALIZATION] Android localization foundation and language packs #102 localization merge, Localize the Android app: string resources and nine language packs (#102) #106). CI green on both.
• Plan and rulings: docs/superpowers/plans/2026-10-04-servicetag-1.7.1/.
• Per the ruling, there is no 1.7.1 release: its content ships in 1.8.0 together with [1.8.0][LOCALIZATION] Android localization foundation and language packs #102 and, when done, [1.8.0][HOME ASSISTANT][UX] Browse and pick boolean entities during season-sync setup #105 (1.7.2). The 1.7.1 plan's P4 (version bump, versioning.md row, release notes) is superseded by 1.8.0's.
• One /v1 behaviour change for 1.8.0's notes: a malformed schedule body (a key with no value) is 400 where it was 500 ([1.7.1][BUG][API] Schedule POST/PATCH answers 500 on a body with a key and no value #94).
• Open before 1.8.0 is cut: the connected suite (R2) on emulator-5554 for the [1.7.1][UI/UX] Maintenance tab and Settings cleanup; move Reminder health to Utilities #103 device classes, which no CI job compiles or runs.

Suggested tracker edits: mark the 1.7.1 section's three issues done, and note that 1.7.1 and 1.7.2 fold into 1.8.0.

---

Generated by Claude Code

[GonzRon]

ServiceTag 1.8.0 (versionCode 21) RELEASED 2026-10-05: tag servicetag-v1.8.0 → 50bc0328, branch release/1.8, master f289a901. It carries #102 (nine more languages), #94 #99 #101 #103 and #105; no schema or format change. Proofs on the tagged commit: dry run, unit gate from scratch, lint, the Python suites, the complete connected suite (78 classes, 430 tests, 0 failures, 0 skips), the picker proof against a real Home Assistant (9 of 9), the 1.7.0 → 1.8.0 in-place upgrade with the token surviving, CI. The published APK is verified (one signer, the same certificate, 1.8.0 / 21, byte-identical code to the gated candidate). #105 closed. The tracker body is updated to the 1.8.0 baseline; no next release train is promoted yet.

[GonzRon]

1.8.0 follow-up 2026-10-05: both phones now run ServiceTag 1.8.0 / code 21, each upgraded in place from 1.7.0 with the verified published APK (same uid and install time, every count and route unchanged, the reminder alarm intact). The production phone carried a saved Home Assistant connection across: the first real-phone record of the token surviving an upgrade. Evidence on master. PR #111 is merged: the repository now carries its commit rules (CLAUDE.md) and CI checks every pull request's own commits.