fix(pii): remove overly broad context keywords from PII recognizers

bootstrap/sql/migrations/native/1.12.12/mysql/schemaChanges.sql

@@ -0,0 +1,4 @@
+-- PII recognizer context keyword cleanup: remove overly broad context keywords
+-- (e.g. "code", "security", "address", "name", "call", "check", "save", "social")
+-- that caused false-positive PII classification on non-PII columns.
+-- Handled by Java data migration in v11212.MigrationUtil.removeBroadPiiContextKeywords.

bootstrap/sql/migrations/native/1.12.12/postgres/schemaChanges.sql

@@ -0,0 +1,4 @@
+-- PII recognizer context keyword cleanup: remove overly broad context keywords
+-- (e.g. "code", "security", "address", "name", "call", "check", "save", "social")
+-- that caused false-positive PII classification on non-PII columns.
+-- Handled by Java data migration in v11212.MigrationUtil.removeBroadPiiContextKeywords.

bootstrap/sql/migrations/native/1.13.1/mysql/schemaChanges.sql

@@ -29,3 +29,8 @@ CREATE INDEX worksheet_entity_name_index ON worksheet_entity (name);
 -- learning_resource_entity is intentionally omitted: its `name` is varchar(3072),
 -- which exceeds MySQL's 3072-byte index key limit (utf8mb4), and the table is small
 -- enough that the reindex cursor sort is not a concern.
+
+-- PII recognizer context keyword cleanup: remove overly broad context keywords
+-- (e.g. "code", "security", "address", "name", "call", "check", "save", "social")
+-- that caused false-positive PII classification on non-PII columns.
+-- Handled by Java data migration in v1131.MigrationUtil.removeBroadPiiContextKeywords.

bootstrap/sql/migrations/native/1.13.1/postgres/schemaChanges.sql

@@ -30,3 +30,8 @@ CREATE INDEX IF NOT EXISTS worksheet_entity_name_index ON worksheet_entity (name
 -- learning_resource_entity is intentionally omitted: its `name` is varchar(3072), too
 -- wide to fit a btree index row, and the table is small enough that the reindex cursor
 -- sort is not a concern.
+
+-- PII recognizer context keyword cleanup: remove overly broad context keywords
+-- (e.g. "code", "security", "address", "name", "call", "check", "save", "social")
+-- that caused false-positive PII classification on non-PII columns.
+-- Handled by Java data migration in v1131.MigrationUtil.removeBroadPiiContextKeywords.