Managed Tab Versioning Recap + Ginger Shot Recipe

TL;DR

• Noted a bug: “Help 2” agent shows latest version (1.1.0) on master, but should show 1.0.0 on the 583885-aryer-fe-show-latest-duplicate branch
• Recapped sync call with Agent 1366: decided to always show the pinned version in the Managed tab instead of latest, to avoid user confusion between Enabled and Managed tabs
• Laid out requirements for show, edit, duplicate, and list pages regarding which version (pinned vs latest) to display, with some items already merged/done
• Made a ginger-turmeric shot recipe with lemon, olive oil, and honey

Bug: Help 2 agent version mismatch

On master, the Help 2 agent shows the latest version (1.1.0). It should instead show 1.0.0 on the 583885-aryer-fe-show-latest-duplicate branch.

Recap for Agent 1366: Managed Tab Versioning Decisions

Thanked Agent 1366 for the sync call and put together a recap to carry into the relevant issues. Items in the Managed tab can fall into one of three states: enabled at both project and group levels, enabled only at the group level, or created in the project but not yet enabled at either level.

I’d originally figured that always showing the latest version in the Managed tab made sense, since it effectively acts as a subset of the AI Catalog for items owned by the project. The problem is that item data is fetched via the URL id parameter, so there’s no way to tell whether the user came from the Enabled or Managed tab — meaning we can’t choose which version to display, and it defaults to the pinned version. This worked fine for not-yet-enabled items, but not for enabled ones.

Decision: always show the pinned version, since it would be confusing for a user to see the pinned version from the Enabled tab and then a different (latest) version from the Managed tab for the same item. The existing component architecture should be reconsidered, as this was a significant blocker, but showing only pinned versions works around it for now — provided the following requirements are implemented:

Show page requirements: display one of two info banners (Agent 1366’s issue linked) — either “this item needs to be approved by a TLG owner” (not enabled anywhere) or “this item needs to be enabled in a project in order to be used” (approved by a TLG owner but not enabled at the project level). In the project namespace, show the project-level pinned version if available, otherwise the group-level pinned version, otherwise the latest version (centralized logic introduced in a linked MR; a follow-up issue was created to implement this logic elsewhere as needed). The update banner should only display in its namespace once an item is enabled there — done.

Edit page requirements — done: always show the latest version to avoid a disconnect in version lineage (removing the Edit button was considered, but the /edit route would need the same complex routing logic) — merged. Also show a warning banner when editing a pinned version that isn’t the latest — merged.

Duplicate page requirements: show the same version as the show page (draft MR linked).

List page (project namespace) requirements: the “Update available” badge should appear in the Managed tab list (issue created).

Group namespace: no changes needed for either the list or item-level views — done.

Ginger Shot Recipe

Add grated ginger and grated turmeric to cold water, with plenty of black pepper and cayenne. Bring to a boil, then simmer for 20 minutes. Pour into small 4-ounce jars and cool in the fridge, then add a 1/2 lemon squeeze, 3 tsp olive oil, and 1-2 tsp honey.