toga-ai 1.0.948 → 1.0.949

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -28,9 +28,9 @@ Nothing is built. This doc records the agreed shape so the next session does not
28
28
 
29
29
  ## How it works (the agreed design)
30
30
 
31
- 1. **Corporate persona.** Move the standard laptop bundle(s) out of the shared persona into a new
32
- **Corporate** persona, and attach it with a **single `Locations_Personas` row on sector `J00000`
33
- (`Locations.id = 52`)**. Effective-persona resolution unions `Users_Personas`, the user's own
31
+ 1. **Corporate persona.** Move the standard laptop bundle(s) out of **Non-Levy (persona 40)** into a
32
+ new **Corporate** persona, and attach it with a **single `Locations_Personas` row on sector
33
+ `J00000` (`Locations.id = 52`)**. Effective-persona resolution unions `Users_Personas`, the user's own
34
34
  `Locations_Personas`, and their **sector's** (the 5-level walk), so every cost center under
35
35
  `J00000` inherits it — including ones Compass adds on a later daily import.
36
36
  2. **Field persona.** It **cannot** use `Locations_Personas`: "everyone except sector 52" is not a
@@ -42,18 +42,27 @@ Nothing is built. This doc records the agreed shape so the next session does not
42
42
  4. **No `isActive` filter is needed.** No inactive cost center under `J00000` has a single active
43
43
  user, so attaching at the sector only ever reaches real people.
44
44
 
45
- ## Prod state observed 2026-10-05 (⚠ conflicts with the refactor doc — re-verify before building)
45
+ ## Where the laptop bundles live (prod `Client_Compass`, verified 2026-10-05)
46
46
 
47
- A read of prod `Client_Compass` on 2026-10-05 found persona **1 still named "All"**, still holding
48
- **all 23 bundles**, every US user on it, and **no `Locations_Personas` row for sector 52** (the table
49
- is used at sector level for 16 other sectors, e.g. Levy sector 55 → persona 24). The standard laptop
50
- was bundle **187** "Compass Standard HP ZBOOK 8 Laptop (Preferred)"; persona 1 also held **188** HP
51
- Ebook Flip (inactive), **192** HP Pro Mini 400 G9, **195** Developer ZBOOK.
47
+ The standard laptop bundles sit in **persona 40 "Non-Levy"** (number 42) — not in persona 1, which is
48
+ **Base** and carries only the 9 kits Levy also holds. See
49
+ [Persona Refactor](../workflows/persona-refactor-migration.md) for the three-way split.
52
50
 
53
- That contradicts [Persona Refactor](../workflows/persona-refactor-migration.md), which records the
54
- three-way split (Base / Non-Levy id 40 / Levy 24) as applied and verified on prod 2026-09-17.
55
- **One of the two is reading the wrong environment — resolve it before writing any migration.** Any
56
- plan written against "persona 40 / Non-Levy" must be re-checked against prod first.
51
+ | Bundle | Name | Note |
52
+ |---|---|---|
53
+ | 187 | Compass Standard HP ZBOOK 8 Laptop (Preferred) | |
54
+ | 188 | Compass Hybrid HP Ebook 8 Flip (Travel) | `isActive = 0` |
55
+ | 192 | HP PRO MINI 400 G9 | |
56
+ | 195 | Compass Developer HP ZBOOK POWER | |
57
+
58
+ **All four are attached to persona 12 "MITS Team" as well**, so the split must move/handle **both**
59
+ personas — doing it on Non-Levy alone leaves MITS Team seeing the old laptop.
60
+
61
+ There is still **no `Locations_Personas` row for location 52**, so nothing inherits at that sector
62
+ today. The table is already used this way for other sectors (e.g. Levy sector 55 → persona 24).
63
+
64
+ **Open question — unanswered by the client:** which of **187 / 192 / 195** count as "the standard
65
+ laptops" that stay corporate-only. Settle that before writing the migration.
57
66
 
58
67
  ## Gotchas
59
68
 
@@ -73,5 +82,9 @@ plan written against "persona 40 / Non-Levy" must be re-checked against prod fir
73
82
  ## Change history
74
83
  - 2026-10-05 — Created. Recorded the agreed corporate/field split (Corporate attached at sector
75
84
  `J00000` via one `Locations_Personas` row; Field assigned in `PeopleFile` and skipped under
76
- `J00000`; the 79-row per-sector alternative rejected) and the 2026-10-05 prod read that conflicts
77
- with the persona-refactor doc. Nothing built. (bala)
85
+ `J00000`; the 79-row per-sector alternative rejected) and the prod bundle locations verified the
86
+ same day: laptops 187 / 188 / 192 / 195 live in **Non-Levy (40)** and are also on **MITS Team
87
+ (12)**, and location 52 still has no `Locations_Personas` row. An earlier draft of this doc quoted
88
+ a **2026-09-15** persona read (persona 1 = "All", 23 bundles) as if it were current and called it a
89
+ conflict with the refactor doc — it was simply taken two days before the refactor went live on
90
+ 2026-09-17. Removed; the refactor docs are correct. Nothing built. (bala)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "toga-ai",
3
- "version": "1.0.948",
3
+ "version": "1.0.949",
4
4
  "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
5
5
  "keywords": [
6
6
  "claude",