thoughtleaders-cli 0.9.10__tar.gz → 0.9.12__tar.gz

{thoughtleaders_cli-0.9.10 → thoughtleaders_cli-0.9.12}/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "tl-cli",
-  "version": "0.9.10",
+  "version": "0.9.12",
   "description": "ThoughtLeaders CLI — query sponsorship deals, channels, brands, uploads, and intelligence from the terminal",
   "author": {
     "name": "ThoughtLeaders",

{thoughtleaders_cli-0.9.10 → thoughtleaders_cli-0.9.12}/AGENTS.md

@@ -88,10 +88,12 @@ The version string is defined in three files and all three must be updated toget
 
 ## Creating a release
 
-A "release" means using the `gh` command to create a release on GitHub, named like the current package version number.
+A "release" means using the `gh` command to create a release on GitHub, tagged and titled `v<version>` (e.g. `v0.9.11`). The `v` prefix is mandatory: the PyPI publish workflow only runs for `v*` tags, and a release without it fails with an environment protection rule error.
 
 Warn the user if they are creating a release and the latest commit didn't bump the version number, and ask for confirmation before releasing.
 
+Release notes are written by hand for the user, never with `--generate-notes` (that yields only a compare link). Follow the style of previous releases: a `##` heading naming the change from the user's perspective, a short prose explanation of what changed and why it matters, a usage example where one helps, and a closing line on what the user has to do (e.g. `tl setup claude` to pick up skill changes, or nothing). Describe user-visible behaviour only — same rules as commit messages and skills apply, so no internal architecture or server details.
+
 ## Coding
 
 * Do not reference internal architecture of the ThoughtLeaders app in comments or skills. Specifially: do not reference internal table names, field names, API endpoints, Python modules or functions (including the sanitizer).

{thoughtleaders_cli-0.9.10 → thoughtleaders_cli-0.9.12}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: thoughtleaders-cli
-Version: 0.9.10
+Version: 0.9.12
 Summary: ThoughtLeaders CLI — query sponsorship data, channels, brands, and intelligence
 Project-URL: Homepage, https://thoughtleaders.io
 Project-URL: Repository, https://github.com/ThoughtLeaders-io/thoughtleaders-cli

{thoughtleaders_cli-0.9.10 → thoughtleaders_cli-0.9.12}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "thoughtleaders-cli"
-version = "0.9.10"
+version = "0.9.12"
 description = "ThoughtLeaders CLI — query sponsorship data, channels, brands, and intelligence"
 readme = "README.md"
 license = "MIT"

{thoughtleaders_cli-0.9.10 → thoughtleaders_cli-0.9.12}/skills/tl/SKILL.md

@@ -88,11 +88,11 @@ Other key concepts:
 - **Adspots** — types of ads a channel is willing to publish (e.g. mention, dedicated video, product placement). Returned by `tl channels show`; each carries price/cost.
 - **Profiles** — actors that own sponsorship records on behalf of either side of a deal. A profile is either buyer-side or seller-side:
   - *Buyer-side (brand) profiles* — represent a sponsoring brand. Each brand profile has an M2M link to at most one `Brand` record (which are the actual advertiser identities). On a sponsorship, `advertiser_profile` is the buyer-side profile, and `advertiser_id` is the buyer-side user who created the record — the advertiser is always the buyer/brand side, never the YouTube creator (the channel hangs off `ad_spot_id`).
-  - *Seller-side (publisher) profiles* — attached to a `Publication`, which in turn owns one or more `Channel` records. A channel's adspots therefore inherit ownership through `channel.publication.profile`.
+  - *Seller-side (publisher) profiles* — represent one or more `Channel` records through the `thoughtleaders_profile_channels` link. Representation is not deal ownership: each adspot names its own seller (`ad_spot.publisher`, a user), so a channel's deals belong to whoever sold them, not to everyone who represents the channel.
   - **How to tell them apart** — three signals on the `thoughtleaders_profile` row, used in this order:
     1. **`persona`** (canonical) — `1=Brand`, `4=Media Agency`, `3=Talent Manager` are buyer-side; `2=Creator`, `5=Creator Service` are seller-side. May be null on legacy rows.
     2. **`is_advertiser` / `is_publisher`** booleans — feature flags; either or both can be true for staff-style profiles, but on normal user profiles they reliably mark side.
-  - Org scoping for sponsorships is profile-mediated: a sponsorship belongs to your org if **either** `advertiser_profile.organization` (brand side) **or** `ad_spot.channel.publication.profile.organization` (publisher side) matches yours.
+  - Org scoping for sponsorships is profile-mediated: a sponsorship belongs to your org if **either** `advertiser_profile.organization` (brand side) **or** the adspot seller's organization — `ad_spot.publisher` → that user's profile → `organization` (publisher side) — matches yours. Representing the channel does not by itself surface its deals; only a `sees_all_deals` link on `thoughtleaders_profile_channels` widens the publisher side to every deal on that channel.
 - **MSN** (Media Selling Network) — the ~12k YouTube channels that have opted in to receive sponsorship offers. A channels is in the MSN group if the `channel.media_selling_network_join_date` field is not null.
 - **MBN** (Media Buying Network) — the brand-side counterpart to MSN: brand profiles that have opted in to receive proposed sponsorships. A profile is in the MBN group if the `profile.media_buying_network_join_date` field is not null.
 - **TPP** (ThoughtLeaders Partner Program, a.k.a. "TL channels") — the ~170 channels TL has the closest working relationship with. A channel is in the TPP group if `channel.is_tpp` is True. **Prefer TPP channels when booking**: they respond fastest, are the easiest to close, and don't need an outreach round-trip — treat them as immediately bookable. TPP is a strict subset of MSN, so the same booking rules (one active mention adspot, etc.) apply.
@@ -521,7 +521,6 @@ If unsure about what information to find where, read the [references/postgresql-
 - `Postgres channel.id` ↔ `ES channel.id` (on article docs) ↔ `Firebolt article_metrics.channel_id` / `channel_metrics.id`
 - `Postgres adlink.article_id` is `<channel_id>:<youtube_id>` — same as ES `_id`. Strip the prefix to get `Firebolt article_metrics.id`.
 - `Postgres brand.id` ↔ ES `sponsored_brand_mentions[]` / `organic_brand_mentions[]`.
-- `publication_id` is **deprecated** — don't use it.
 
 **Snapshots are sparse**, especially for older videos. Don't assume two arbitrary dates have data points. For approximations, prefer `tl snapshots` which already implements the project's interpolation logic; falling back to raw `tl db fb` means you handle gaps yourself.
 

{thoughtleaders_cli-0.9.10 → thoughtleaders_cli-0.9.12}/skills/tl/references/elasticsearch-schema.md

@@ -59,7 +59,7 @@ Filter with `{"term": {"doc_type": "article"}}`. Coverage percentages are live `
 | `content_type` | keyword | `longform` / `short` / `live` — the complete value set. ~71% of docs; older docs have none (missing ≠ longform). Podcast/RSS docs have no `content_type`. |
 | `content_aspects` | keyword | Flags: `podcast`, `paid_promotion`, `unlisted` — the complete value set. Only ~2.6% of docs carry any. |
 | `hashtags` | keyword | Hashtags from the video description, stored **without the leading `#`** and lowercase (e.g. `marchmadness`); non-Latin tags appear percent-encoded (`%D0%B0…`) (~32%) |
-| `channel` | object | Embedded channel subset: `channel.id`, `channel.content_category`, `channel.format`, `channel.publication_id`, `channel.country`, `channel.language` — no text fields, no metrics. This is where a video's language/country/format/category live (top-level `language`, `country`, `format`, `content_category` exist only on channel docs). |
+| `channel` | object | Embedded channel subset: `channel.id`, `channel.content_category`, `channel.format`, `channel.country`, `channel.language` — no text fields, no metrics. This is where a video's language/country/format/category live (top-level `language`, `country`, `format`, `content_category` exist only on channel docs). |
 
 ⚠️ **Channel-doc fields that look like video fields but match 0 video docs:** `total_views`, `engagement`, `duration_live`/`duration_longform`/`duration_shorts`, `language`, `country`, `format`, `content_category`, `face_on_screen`. They live on channel docs (see below); on video docs use the embedded `channel.*` subset where available.
 
@@ -108,7 +108,8 @@ Contains a denormalized subset of the PostgreSQL channel data.
 | `media_selling_network_join_date` | date | MSN join date; non-null = MSN member (~1%) |
 | `has_outreach_email` | boolean | Has contact email (100%) |
 | `outreach_email` | text | Contact email (~45%) |
-| `social_links` | text | Flat array of the channel's profile URLs (~47%), e.g. `["https://twitter.com/…", "https://instagram.com/…", "https://discord.gg/…"]`. Source is a per-platform map plus a catch-all `_other` map for unrecognized platforms; in ES all of it is flattened into this one URL array (the `_other` URLs are folded in, the platform names are dropped). Occasional stray entries (bare emails, nested arrays) exist. |
+| `social_links` | text | Flat array of the channel's known profile links as **canonical keys** — lowercase `host/path` with no scheme, no `www.`, no query string, and `x.com` spelled as `twitter.com`, e.g. `["twitter.com/mrbeast", "instagram.com/mrbeast", "linktr.ee/foo"]` (~47%, growing). Sourced from the `all_social_links` accumulator (About-page scrapes plus web-search discoveries); platform names are dropped, e-mails never appear. |
+| `social_links.canonical` | text | Subfield of the above with a path-segment analyzer: one token per URL segment, subdomain-insensitive host. `{"match_phrase": {"social_links.canonical": "twitch.tv/ludwig"}}` is the precise way to ask "which channels carry exactly this profile link" — it matches `m.twitch.tv/ludwig` and deep paths under the profile, but never a channel that merely mentions the same words in different links. Prefer it over matching the parent field when the query is a `domain/handle` pair. |
 | `male_share` | byte | Male audience % — only ~1.6% of channel docs have demographic data |
 | `usa_share` | byte | US audience % — same ~1.6% coverage |
 | `device` | object | Audience device demographics where known: `device.primary` (most common device) and `device.share` (per-device % map). Very sparse (~0.2%). |
@@ -282,5 +283,4 @@ The `transcript` field's `_source` is **YouTube timed-text caption XML**, not pl
 - `sponsored_brand_mentions` and `organic_brand_mentions` are keyword arrays — use `term` queries.
 - For brand mention details (position, snippet, detection_tool), the data is in the `brand_mentions` nested field.
 - **Stored-only fields** — retrievable in `_source` but invisible to `exists`/`term`/`match` (queries on them silently match 0 docs): `url`, `image_url`, `es_index_tag`, `not_sponsored_by`.
-- **`publication_id` is deprecated** — don't use for joins.
 - No write access. The CLI only exposes `_search` against `tl-platform-*`.

{thoughtleaders_cli-0.9.10 → thoughtleaders_cli-0.9.12}/skills/tl/references/postgres-schema.md

@@ -353,13 +353,18 @@ LIMIT 50 OFFSET 0
 
 ## `thoughtleaders_profile_channels` (Profile ↔ Channel M2M)
 
-| Column | Type |
-|--------|------|
-| `id` | int PK |
-| `profile_id` | int FK |
-| `channel_id` | int FK |
+Which channels a seller-side profile represents. One row per profile/channel pair.
 
-Note: separate from the adspot publisher relationship. Not always in sync.
+| Column | Type | Description |
+|--------|------|-------------|
+| `id` | int PK | |
+| `profile_id` | int FK | → `thoughtleaders_profile.id` |
+| `channel_id` | int FK | → `thoughtleaders_channel.id` |
+| `sees_all_deals` | boolean | When true, the profile's organization sees **every** deal on the channel, not only the deals it sold itself. Absent from the sandbox views, so only a full-access context can read it. |
+| `created_where` | varchar | What created the link. NULL on every link that predates the column. |
+| `created_at` | timestamptz | When the link was created. NULL on every link that predates the column — filtering or ordering on it silently drops that whole population. |
+
+⚠️ **Representation is not deal ownership.** A deal's seller is the adspot's own publisher (`thoughtleaders_adspot.publisher_id` → `auth_user`, then `thoughtleaders_profile.user_id` for the org). Joining sponsorships to an org through this table alone over-reports — only a `sees_all_deals = true` row widens the seller side to all of a channel's deals. `publisher_id` is scrubbed from the sandbox adspot view, so the seller-side hop is only queryable from a full-access role.
 
 ## Example queries
 

{thoughtleaders_cli-0.9.10 → thoughtleaders_cli-0.9.12}/skills/tl-save-report/references/intelligence_filterset_schema.json

@@ -362,18 +362,6 @@
       "uniqueItems": true,
       "description": "Article IDs to exclude (composite `<channel_id>:<youtube_id>` form). Pairs with a predicate-style FilterSet — useful for 'videos matching X, except these specific ones'.",
       "_tl_django_m2m": "FilterSet.exclude_articles via FiltersetExcludeArticles"
-    },
-
-    "networks": {
-      "type": ["array", "null"],
-      "items": { "type": "integer", "minimum": 1 },
-      "uniqueItems": true,
-      "_tl_django_m2m": "FilterSet.networks → thoughtleaders.Publication"
-    },
-    "exclude_networks": {
-      "type": ["array", "null"],
-      "items": { "type": "integer", "minimum": 1 },
-      "uniqueItems": true
     }
   },
 

{thoughtleaders_cli-0.9.10 → thoughtleaders_cli-0.9.12}/skills/tl-save-report/references/sponsorship_filterset_schema.json

@@ -58,18 +58,6 @@
       "_tl_django_m2m": "FilterSet.exclude_brands via FilterSetExcludeBrand"
     },
 
-    "networks": {
-      "type": ["array", "null"],
-      "items": { "type": "integer", "minimum": 1 },
-      "uniqueItems": true,
-      "_tl_django_m2m": "FilterSet.networks → thoughtleaders.Publication"
-    },
-    "exclude_networks": {
-      "type": ["array", "null"],
-      "items": { "type": "integer", "minimum": 1 },
-      "uniqueItems": true
-    },
-
     "start_date": {
       "type": ["string", "null"],
       "format": "date",

{thoughtleaders_cli-0.9.10 → thoughtleaders_cli-0.9.12}/src/tl_cli/__init__.py

@@ -1,3 +1,3 @@
 """ThoughtLeaders CLI — query sponsorship data, channels, brands, and intelligence."""
 
-__version__ = "0.9.10"
+__version__ = "0.9.12"

{thoughtleaders_cli-0.9.10 → thoughtleaders_cli-0.9.12}/src/tl_cli/output/formatter.py

@@ -215,7 +215,7 @@ def _detect_numeric_columns(results: list[dict], columns: list[str]) -> set[str]
                 numeric.discard(col)
     # Don't treat ID-like columns as numeric
     for col in list(numeric):
-        if col.endswith("_id") or col == "id" or "publication" in col:
+        if col.endswith("_id") or col == "id":
             numeric.discard(col)
     # Columns where every sampled value was None/empty aren't meaningfully numeric
     for col in list(numeric):