agrs-sequelize-sdk 1.4.39 → 1.4.41

package/models/Article.js

@@ -31,6 +31,12 @@ module.exports = (sequelize, DataTypes) => {
         type: DataTypes.STRING(1024),
         allowNull: true,
       },
+      sourceCampaignId: {
+        type: DataTypes.STRING,
+        allowNull: true,
+        comment:
+          "FB campaign id of the campaign that originally created this article. Populated by Tarzo mirror on create-success so duplicate-as-reuse can find the source when this article is reused. Nullable — not all articles have a known source (legacy rows, articles whose source campaign was deleted).",
+      },
       feed: {
         type: DataTypes.STRING,
         allowNull: false,
@@ -177,6 +183,10 @@ module.exports = (sequelize, DataTypes) => {
           unique: true,
           fields: ['providerId', 'feed'],
           name: 'unique_provider_per_feed'
+        },
+        {
+          fields: ['sourceCampaignId'],
+          name: 'idx_article_source_campaign_id'
         }
       ]
     }

package/models/PublicApiIdempotencyCache.js

@@ -89,15 +89,33 @@ module.exports = (sequelize, DataTypes) => {
     {
       tableName: "PublicApiIdempotencyCache",
       indexes: [
-        // Primary lookup: (user_id, key). UNIQUE so INSERT ... ON CONFLICT
-        // DO NOTHING atomically claims the key for the first caller — the
-        // "9 concurrent retries" burst case where only ONE request should
-        // execute the underlying work.
-        { unique: true, fields: ["user_id", "key"] },
+        // Primary lookup: (user_id, key). UNIQUE so Postgres resolves N
+        // concurrent claims atomically — the loser hits a unique violation,
+        // Sequelize's findOrCreate catches it, re-finds the winner's row, and
+        // returns created=false. That is what makes exactly ONE of the "9
+        // concurrent retries" execute the work while the rest get 409.
+        //
+        // THIS INDEX IS THE ENTIRE FEATURE. Without it every concurrent INSERT
+        // succeeds and every retry re-runs the operation. Verified in prod on
+        // 2026-07-12: index absent -> a 9-way burst gave 5 executions; index
+        // present (local) -> exactly 1.
+        //
+        // Named explicitly so the migration that backfills it on already-created
+        // tables targets the same index. sequelize.sync() runs with alter:false
+        // in prod (server.js gates it on DB_COLUMN_TYPE_UPDATE), so it creates
+        // the table but does NOT add indexes to a table that already exists.
+        {
+          name: "PublicApiIdempotencyCache_user_id_key_uniq",
+          unique: true,
+          fields: ["user_id", "key"],
+        },
         // Sweep index — cron does `DELETE WHERE expires_at < NOW()`. Not
         // partial (would need to update after every insert); regular
         // btree is fine for the sweep pattern.
-        { fields: ["expires_at"] },
+        {
+          name: "PublicApiIdempotencyCache_expires_at_idx",
+          fields: ["expires_at"],
+        },
       ],
     }
   );

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agrs-sequelize-sdk",
-  "version": "1.4.39",
+  "version": "1.4.41",
   "main": "index.js",
   "scripts": {
     "start": "node index.js",