chore: 初始开源发布

iotlcm-worker-svr：异步执行中枢（RabbitMQ 消费者 + 全量同步编排）。 - Go module：iotlcm-worker-svr → git.5iot.com/iotlcm-public/iotlcm-worker-svr（214 文件） - 凭据与内部标识脱敏：MySQL/Redis 凭据、私网与生产 IP、内网域名、库名 xiujie_admin → iotlcm、哨兵名占位 - 159 处真实手机号 → 合法 11 位编造号（保留号段与后 4 位，维持互异，不破坏「校验 MSISDN 格式」等测试断言） - 移除内部资产：CI 触发器、Jenkins 触发测试文档、预演门禁与镜像 digest 记录 - Dockerfile 改用公共基础镜像（golang:1.25-alpine → alpine:3.23），移除写死的 git 凭据 - README 重写（架构/全量同步模型/配置/已知失败），补 Apache-2.0 LICENSE，LF 行尾 + .gitattributes 已知：3 个测试包在源仓同一提交上同样失败（client/upstream、 service/allocate、service/inbound），属既有缺陷，本仓未引入亦未修复。
2026-10-22 16:37:56 +08:00
commit 2bec257289
361 changed files with 71524 additions and 0 deletions
@@ -0,0 +1,79 @@
+package model
+
+// TrafficUsageSimCard is the basic card data needed when writing usage to TDengine.
+type TrafficUsageSimCard struct {
+	Iccid       string `json:"iccid"`
+	PackageCode string `json:"packageCode"`
+}
+
+// TrafficUsageDailyRetryMessage is the retry message for daily traffic usage.
+type TrafficUsageDailyRetryMessage struct {
+	UsageMb   *float64            `json:"usageMb,omitempty"`
+	Attempt   int                 `json:"attempt,omitempty"`
+	LastError string              `json:"lastError,omitempty"`
+	SimKey    *SimKey             `json:"simKey"`
+	Card      TrafficUsageSimCard `json:"card"`
+	// QueryDate format: yyyyMMdd.
+	QueryDate string `json:"queryDate"`
+}
+
+// TrafficUsageMonthlyRetryMessage is the retry message for monthly traffic usage.
+type TrafficUsageMonthlyRetryMessage struct {
+	UsageMb   *float64            `json:"usageMb,omitempty"`
+	Attempt   int                 `json:"attempt,omitempty"`
+	LastError string              `json:"lastError,omitempty"`
+	SimKey    *SimKey             `json:"simKey"`
+	Card      TrafficUsageSimCard `json:"card"`
+	// QueryDate format: yyyyMM.
+	QueryDate string `json:"queryDate"`
+}
+
+// TrafficUsageMonthlyStartMessage starts one full monthly usage run.
+// Admin publishes this command; Worker owns the card scan and Redis production.
+// A nil Scope (or one whose channels normalize to empty) is a full sync.
+type TrafficUsageMonthlyStartMessage struct {
+	RunID       string     `json:"runId"`
+	Operation   string     `json:"operation"`
+	QueryMonth  string     `json:"queryMonth"`
+	TriggeredAt string     `json:"triggeredAt"`
+	Scope       *SyncScope `json:"scope,omitempty"`
+}
+
+// TrafficUsageDailyStartMessage starts one full daily usage run.
+// Admin publishes this command; Worker owns the card scan and Redis production.
+// A nil Scope (or one whose channels normalize to empty) is a full sync.
+//
+// QueryDate is yyyyMMdd. The producer carries it through zset.Task.QueryMonth,
+// which is a period identifier rather than a month name; see that field's doc.
+type TrafficUsageDailyStartMessage struct {
+	RunID       string     `json:"runId"`
+	Operation   string     `json:"operation"`
+	QueryDate   string     `json:"queryDate"`
+	TriggeredAt string     `json:"triggeredAt"`
+	Scope       *SyncScope `json:"scope,omitempty"`
+}
+
+// TrafficUsageMonthlyHistoryStartMessage starts one full monthly usage history
+// run. It writes the TDengine monthly table, which is a different target from
+// TrafficUsageMonthlyStartMessage (the current-month snapshot written to MySQL).
+//
+// QueryMonth is yyyyMM and names the month being backfilled, which is the
+// previous month rather than the current one.
+type TrafficUsageMonthlyHistoryStartMessage struct {
+	RunID       string     `json:"runId"`
+	Operation   string     `json:"operation"`
+	QueryMonth  string     `json:"queryMonth"`
+	TriggeredAt string     `json:"triggeredAt"`
+	Scope       *SyncScope `json:"scope,omitempty"`
+}
+
+// OperationPreviousDayUsageFullSync identifies a daily usage run. It is the one
+// string that Admin publishes, Worker produces, and contract.SyncKindForOperation
+// maps to the traffic_usage_daily sync kind, so it lives here rather than in
+// either side's logic package.
+const OperationPreviousDayUsageFullSync = "previous_day_usage_full_sync"
+
+// OperationPreviousMonthUsageFullSync identifies a monthly usage history run.
+// It is deliberately distinct from current_month_usage_full_sync, which fills
+// the MySQL current-month snapshot instead of the TDengine monthly table.
+const OperationPreviousMonthUsageFullSync = "previous_month_usage_full_sync"