trueppm-api 0.4.0b2__py3-none-any.whl

trueppm_api/apps/profiles/migrations/0001_squashed_0004_userprofile_role_context.py

@@ -0,0 +1,125 @@
+# Generated by Django 5.2.14 on 2026-06-23 21:38
+
+import uuid
+
+import django.db.models.deletion
+from django.conf import settings
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+    replaces = [
+        ("profiles", "0001_initial"),
+        ("profiles", "0002_userprofile_hidden_views"),
+        ("profiles", "0003_projectvisit"),
+        ("profiles", "0004_userprofile_role_context"),
+    ]
+
+    initial = True
+
+    dependencies = [
+        ("projects", "0086_board_card_search_trgm"),
+        migrations.swappable_dependency(settings.AUTH_USER_MODEL),
+    ]
+
+    operations = [
+        migrations.CreateModel(
+            name="ProjectVisit",
+            fields=[
+                (
+                    "id",
+                    models.UUIDField(
+                        default=uuid.uuid4, editable=False, primary_key=True, serialize=False
+                    ),
+                ),
+                (
+                    "visited_at",
+                    models.DateTimeField(help_text="When the user last opened this project."),
+                ),
+                (
+                    "project",
+                    models.ForeignKey(
+                        on_delete=django.db.models.deletion.CASCADE,
+                        related_name="visits",
+                        to="projects.project",
+                    ),
+                ),
+                (
+                    "user",
+                    models.ForeignKey(
+                        on_delete=django.db.models.deletion.CASCADE,
+                        related_name="project_visits",
+                        to=settings.AUTH_USER_MODEL,
+                    ),
+                ),
+            ],
+            options={
+                "verbose_name": "project visit",
+                "verbose_name_plural": "project visits",
+                "indexes": [
+                    models.Index(
+                        fields=["user", "-visited_at"], name="projectvisit_user_recent_idx"
+                    )
+                ],
+                "constraints": [
+                    models.UniqueConstraint(
+                        fields=("user", "project"), name="uq_project_visit_user_project"
+                    )
+                ],
+            },
+        ),
+        migrations.CreateModel(
+            name="UserProfile",
+            fields=[
+                (
+                    "id",
+                    models.UUIDField(
+                        default=uuid.uuid4, editable=False, primary_key=True, serialize=False
+                    ),
+                ),
+                (
+                    "default_landing",
+                    models.CharField(
+                        choices=[
+                            ("auto", "Automatic (based on your role)"),
+                            ("my_work", "My Work"),
+                            ("project_overview", "Project Overview"),
+                            ("portfolio", "Portfolio"),
+                        ],
+                        default="auto",
+                        help_text="Which screen the app opens on. 'auto' uses the role-based policy.",
+                        max_length=20,
+                    ),
+                ),
+                (
+                    "user",
+                    models.OneToOneField(
+                        on_delete=django.db.models.deletion.CASCADE,
+                        related_name="profile",
+                        to=settings.AUTH_USER_MODEL,
+                    ),
+                ),
+                (
+                    "hidden_views",
+                    models.JSONField(blank=True, default=list, help_text="Hidden nav view keys."),
+                ),
+                (
+                    "role_context",
+                    models.CharField(
+                        choices=[
+                            ("pm", "PM"),
+                            ("scrum_master", "Scrum Master"),
+                            ("unified", "Unified Today"),
+                        ],
+                        default="unified",
+                        help_text="Active role-context view: PM, Scrum Master, or Unified Today (#412).",
+                        max_length=12,
+                    ),
+                ),
+            ],
+            options={
+                "verbose_name": "user profile",
+                "verbose_name_plural": "user profiles",
+            },
+        ),
+    ]

trueppm_api/apps/profiles/migrations/0002_userprofile_hidden_views.py

@@ -0,0 +1,17 @@
+# Generated by Django 5.2.14 on 2026-06-16 15:51
+
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+    dependencies = [
+        ("profiles", "0001_initial"),
+    ]
+
+    operations = [
+        migrations.AddField(
+            model_name="userprofile",
+            name="hidden_views",
+            field=models.JSONField(blank=True, default=list, help_text="Hidden nav view keys."),
+        ),
+    ]

trueppm_api/apps/profiles/migrations/0003_projectvisit.py

@@ -0,0 +1,63 @@
+# Generated by Django 5.2.14 on 2026-06-20 15:02
+
+import uuid
+
+import django.db.models.deletion
+from django.conf import settings
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+    dependencies = [
+        ("profiles", "0002_userprofile_hidden_views"),
+        ("projects", "0086_board_card_search_trgm"),
+        migrations.swappable_dependency(settings.AUTH_USER_MODEL),
+    ]
+
+    operations = [
+        migrations.CreateModel(
+            name="ProjectVisit",
+            fields=[
+                (
+                    "id",
+                    models.UUIDField(
+                        default=uuid.uuid4, editable=False, primary_key=True, serialize=False
+                    ),
+                ),
+                (
+                    "visited_at",
+                    models.DateTimeField(help_text="When the user last opened this project."),
+                ),
+                (
+                    "project",
+                    models.ForeignKey(
+                        on_delete=django.db.models.deletion.CASCADE,
+                        related_name="visits",
+                        to="projects.project",
+                    ),
+                ),
+                (
+                    "user",
+                    models.ForeignKey(
+                        on_delete=django.db.models.deletion.CASCADE,
+                        related_name="project_visits",
+                        to=settings.AUTH_USER_MODEL,
+                    ),
+                ),
+            ],
+            options={
+                "verbose_name": "project visit",
+                "verbose_name_plural": "project visits",
+                "indexes": [
+                    models.Index(
+                        fields=["user", "-visited_at"], name="projectvisit_user_recent_idx"
+                    )
+                ],
+                "constraints": [
+                    models.UniqueConstraint(
+                        fields=("user", "project"), name="uq_project_visit_user_project"
+                    )
+                ],
+            },
+        ),
+    ]

trueppm_api/apps/profiles/migrations/0004_userprofile_role_context.py

@@ -0,0 +1,26 @@
+# Generated by Django 5.2.14 on 2026-06-22 01:15
+
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+    dependencies = [
+        ("profiles", "0003_projectvisit"),
+    ]
+
+    operations = [
+        migrations.AddField(
+            model_name="userprofile",
+            name="role_context",
+            field=models.CharField(
+                choices=[
+                    ("pm", "PM"),
+                    ("scrum_master", "Scrum Master"),
+                    ("unified", "Unified Today"),
+                ],
+                default="unified",
+                help_text="Active role-context view: PM, Scrum Master, or Unified Today (#412).",
+                max_length=12,
+            ),
+        ),
+    ]

trueppm_api/apps/profiles/migrations/0005_userprofile_schedule_in_deliver.py

@@ -0,0 +1,20 @@
+# Generated by Django 5.2.15 on 2026-07-07 01:58
+
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+    dependencies = [
+        ("profiles", "0001_squashed_0004_userprofile_role_context"),
+    ]
+
+    operations = [
+        migrations.AddField(
+            model_name="userprofile",
+            name="schedule_in_deliver",
+            field=models.BooleanField(
+                default=False,
+                help_text="Also surface Schedule under Deliver (opt-in, display-only).",
+            ),
+        ),
+    ]

trueppm_api/apps/profiles/migrations/0006_userprofile_date_format_userprofile_timezone.py

@@ -0,0 +1,36 @@
+# Generated by Django 5.2.16 on 2026-07-14 16:54
+
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+    dependencies = [
+        ("profiles", "0005_userprofile_schedule_in_deliver"),
+    ]
+
+    operations = [
+        migrations.AddField(
+            model_name="userprofile",
+            name="date_format",
+            field=models.CharField(
+                choices=[
+                    ("auto", "Automatic (based on your locale)"),
+                    ("iso", "2026-07-14"),
+                    ("us", "Jul 14, 2026"),
+                    ("eu", "14 Jul 2026"),
+                ],
+                default="auto",
+                help_text="Date-format style for all displayed dates. 'auto' follows browser locale.",
+                max_length=8,
+            ),
+        ),
+        migrations.AddField(
+            model_name="userprofile",
+            name="timezone",
+            field=models.CharField(
+                default="auto",
+                help_text="IANA timezone for displaying instant timestamps, or 'auto' to use the browser's detected zone. Display-only; API datetimes stay UTC.",
+                max_length=64,
+            ),
+        ),
+    ]

trueppm_api/apps/profiles/migrations/0007_userpin.py

@@ -0,0 +1,91 @@
+# Generated by Django 5.2.16 on 2026-07-26 00:00
+
+import uuid
+
+import django.db.models.deletion
+from django.conf import settings
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+    dependencies = [
+        ("profiles", "0006_userprofile_date_format_userprofile_timezone"),
+        ("projects", "0126_projectcustomfield_show_on_card_taskcustomfieldvalue"),
+        migrations.swappable_dependency(settings.AUTH_USER_MODEL),
+    ]
+
+    operations = [
+        migrations.CreateModel(
+            name="UserPin",
+            fields=[
+                (
+                    "id",
+                    models.UUIDField(
+                        default=uuid.uuid4, editable=False, primary_key=True, serialize=False
+                    ),
+                ),
+                (
+                    "pinned_at",
+                    models.DateTimeField(
+                        auto_now_add=True,
+                        help_text="When the user pinned this item. Never exposed on a shared payload.",
+                    ),
+                ),
+                (
+                    "program",
+                    models.ForeignKey(
+                        blank=True,
+                        null=True,
+                        on_delete=django.db.models.deletion.CASCADE,
+                        related_name="pins",
+                        to="projects.program",
+                    ),
+                ),
+                (
+                    "project",
+                    models.ForeignKey(
+                        blank=True,
+                        null=True,
+                        on_delete=django.db.models.deletion.CASCADE,
+                        related_name="pins",
+                        to="projects.project",
+                    ),
+                ),
+                (
+                    "user",
+                    models.ForeignKey(
+                        on_delete=django.db.models.deletion.CASCADE,
+                        related_name="pins",
+                        to=settings.AUTH_USER_MODEL,
+                    ),
+                ),
+            ],
+            options={
+                "verbose_name": "user pin",
+                "verbose_name_plural": "user pins",
+                "indexes": [
+                    models.Index(fields=["user", "-pinned_at"], name="userpin_user_recent_idx")
+                ],
+                "constraints": [
+                    models.CheckConstraint(
+                        condition=models.Q(
+                            models.Q(("program__isnull", True), ("project__isnull", False)),
+                            models.Q(("program__isnull", False), ("project__isnull", True)),
+                            _connector="OR",
+                        ),
+                        name="ck_userpin_project_xor_program",
+                    ),
+                    models.UniqueConstraint(
+                        condition=models.Q(("project__isnull", False)),
+                        fields=("user", "project"),
+                        name="uq_userpin_user_project",
+                    ),
+                    models.UniqueConstraint(
+                        condition=models.Q(("program__isnull", False)),
+                        fields=("user", "program"),
+                        name="uq_userpin_user_program",
+                    ),
+                ],
+            },
+        ),
+    ]

trueppm_api/apps/profiles/migrations/0008_remove_userprofile_schedule_in_deliver.py

@@ -0,0 +1,71 @@
+# Generated by Django 5.2.16 on 2026-08-30
+
+from django.db import migrations
+
+
+class Migration(migrations.Migration):
+    """Drop ``UserProfile.schedule_in_deliver`` (ADR-0942 §3, #3137).
+
+    The Schedule-in-Deliver placement opt-in (ADR-0203, #1645) let a user echo the
+    Schedule view into the DELIVER band while it stayed in PLAN. ADR-0942 adopts "one
+    home per item, per render" — a nav item listed twice is two objects to the person
+    using it — so nothing reads the flag any more.
+
+    Removed rather than deprecated to a no-op. A boolean that still round-trips and is
+    read by nothing is documented, echoes back, and lies to every API and MCP client
+    about what the product does; the honest option at pre-1.0 alpha, for a display-only
+    field no rollup, report, export, schedule computation or webhook reads, is deletion
+    and a 400 on a stale write. That 400 does not come for free — DRF's default is to
+    drop an unrecognised key and answer 200 — so it is implemented explicitly by
+    ``UserProfileSerializer.RETIRED_FIELDS``.
+
+    **Rolling-upgrade window.** The Helm API deployment has no ``strategy:`` block, so
+    Kubernetes rolls with the default RollingUpdate and old pods keep serving while the
+    new pod's init container runs ``migrate_locked``. The moment this migration applies,
+    an old pod's ``get_profile_prefs`` — which names its columns explicitly in
+    ``.only(...)``, ``schedule_in_deliver`` among them — selects a column that no longer
+    exists and 500s on ``/auth/me/``, the web shell's bootstrap call. The window is
+    bounded by rollout duration.
+
+    **This window is not confined to single-replica installs.** An earlier draft of
+    this note said it "does not exist on single-replica installs, which is every
+    self-hosted deployment we know of at pre-1.0 alpha" — that premise shifted inside
+    this same release: ``packages/helm/values-prod.yaml``, the shipped production
+    reference values, sets ``replicaCount: 2``, and the API Deployment has no explicit
+    ``strategy:`` overriding Kubernetes' default RollingUpdate, which surges a pod at
+    any replica count >= 1. The 0.4 basic-HA carve-out (epic #3408) makes a 2-replica
+    API tier a realistic, encouraged self-hosted posture for 0.4, not a hypothetical —
+    so this window is expected to fire on that posture, not merely a theoretical edge
+    case (#3782). The trade is still accepted knowingly: the blast radius stays bounded
+    to transient 500s on ``/auth/me/`` for requests landing on an old pod during the
+    rollout window, with no crash-loop and no data loss beyond the already-accepted
+    loss of the boolean preference itself. The rolling-safe shape would have been two
+    releases (drop the code references in N, the column in N+1); this is deliberately
+    one. See the 0.4 upgrade notes
+    (``packages/website/src/content/docs/getting-started/upgrade.md``) for the
+    operator-facing disclosure of this window.
+
+    **What happens to a user who had it on.** Their column is dropped and their
+    preference is gone; the rail renders the calm default (Schedule in PLAN only), which
+    is what every non-opted-in user already saw. Nothing else about their profile
+    changes — this migration touches one column and no other field, row, or default. The
+    need the opt-in served is now met by adjacency and one hop: PLAN sits directly above
+    DELIVER. That is weaker than the opt-in, and ADR-0942 says so; the recorded response
+    to a real complaint is band order or an explicit shortcut affordance, never a
+    restored duplicate.
+
+    No data to preserve and no constraint added, so the constraint-safety gate does not
+    apply. Irreversible in practice: reversing it recreates the column at its ``False``
+    default, not at whatever each user had chosen.
+    """
+
+    dependencies = [
+        ("profiles", "0007_userpin"),
+    ]
+
+    operations = [
+        migrations.RemoveField(
+            model_name="userprofile",
+            name="schedule_in_deliver",
+        ),
+    ]

trueppm_api/apps/profiles/migrations/0009_auth_user_email_upper_idx.py

@@ -0,0 +1,81 @@
+"""Functional index on ``UPPER(auth_user.email)`` for the ``email__iexact`` lookups (#3504).
+
+Seven call sites resolve a person by email on ``auth.User``: the login email
+fallback and password reset (``core``), OIDC account linking (``apps.sso``),
+workspace invite acceptance and the duplicate-member guard (``apps.workspace``),
+inbound Jira assignee mapping (``apps.projects``), and the
+``revoke_api_tokens`` command (``apps.access``).
+
+Six of the seven are served by this index; ``revoke_api_tokens`` is not. It
+matches ``Q(username__iexact=...) | Q(email__iexact=...)`` in one query, and an
+OR across two columns can only use indexes when *both* sides have one — there is
+no ``UPPER(username)`` index, and adding one to speed up an interactive admin
+command is not worth a second functional index on the same table.
+
+**Why a functional index and not ``db_index``.** On PostgreSQL Django compiles
+``iexact`` through ``lookup_cast()`` to ``UPPER("auth_user"."email"::text) =
+UPPER(%s)``. A plain btree on ``email`` indexes the *column*, not that
+expression, so the planner cannot use it — the index has to be built on the same
+``UPPER(email::text)`` expression the query filters on. The SQL above is the
+verbatim expression Django emits, so the two match exactly.
+
+**Why raw SQL.** ``auth.User`` is a ``django.contrib`` model we do not own, so
+``Meta.indexes`` is unavailable. Per CLAUDE.md's migration discipline this is the
+narrow case where the ORM genuinely cannot express the operation. It is
+deliberately **DB-only with no ``state_operations``**: adding the index to
+Django's migration state would describe a model this app does not own and make
+``makemigrations --check`` demand a ``RemoveIndex``.
+
+**Why this app.** No single consumer owns the index — the seven call sites span
+``core``, ``sso``, ``workspace``, ``projects`` and ``access``. ``profiles`` is
+the app whose domain *is* the auth user record (``UserProfile`` is its 1:1
+extension), and it already carries a swappable dependency on
+``AUTH_USER_MODEL``, so it is the natural home for a schema addition to
+``auth_user`` itself.
+
+**Why NOT ``CREATE INDEX CONCURRENTLY``** (this deviates from the SQL proposed on
+the issue, deliberately). ``CONCURRENTLY`` cannot run inside a transaction and
+therefore forces ``atomic = False``. The three existing concurrent-index
+migrations (``projects`` 0090/0100/0105) each justify that cost by table size —
+they build on the largest and highest-volume tables in the schema, where a
+``ShareLock`` is user-visible during a rolling deploy. ``auth_user`` is the
+inverse: ``administration/sizing.md`` puts the envelope at a team of 25 to a team
+of 250, so the table is in the low hundreds of rows and the in-transaction build
+holds its lock for well under a millisecond.
+
+Against that non-benefit, ``atomic = False`` carries a real hazard here.
+Migrations run on container start, and a ``CREATE INDEX CONCURRENTLY`` that
+fails part-way leaves an **INVALID** index behind: the planner ignores it while
+every write still maintains it. Combined with the ``IF NOT EXISTS`` guard below,
+the retry would then *silently skip* the invalid index, record the migration as
+applied, and leave the index permanently non-functional with nothing in the
+output saying so. An atomic build simply rolls back and fails loudly.
+
+An operator running far outside the documented envelope, where the plain build
+would take a noticeable lock, can pre-build the index by hand with
+``CREATE INDEX CONCURRENTLY auth_user_email_upper_idx ON auth_user
+(UPPER(email::text));`` before upgrading — ``IF NOT EXISTS`` then makes this
+migration a verified no-op.
+"""
+
+from __future__ import annotations
+
+from django.db import migrations
+
+_INDEX = "auth_user_email_upper_idx"
+
+
+class Migration(migrations.Migration):
+    dependencies = [
+        ("profiles", "0008_remove_userprofile_schedule_in_deliver"),
+        # auth_user must exist (and be at its final column shape) before we index
+        # an expression over one of its columns.
+        ("auth", "0012_alter_user_first_name_max_length"),
+    ]
+
+    operations = [
+        migrations.RunSQL(
+            sql=(f"CREATE INDEX IF NOT EXISTS {_INDEX} ON auth_user (UPPER(email::text));"),
+            reverse_sql=f"DROP INDEX IF EXISTS {_INDEX};",
+        ),
+    ]