@jungjaehoon/mama-core 2.1.0 → 2.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/db/migrations/{043-add-tool-trace-failure-code.sql → 061-add-tool-trace-failure-code.sql}
RENAMED
|
@@ -1,4 +1,12 @@
|
|
|
1
|
-
-- Migration
|
|
1
|
+
-- Migration 061: tool_traces.failure_code — carry the thrower's closed cause.
|
|
2
|
+
--
|
|
3
|
+
-- WHY 061, NOT 043: live DBs carry schema_version rows 44-60 from a RETIRED
|
|
4
|
+
-- 2026-05/06 migration chain that shared this ledger table. The runner skips
|
|
5
|
+
-- any file numbered at or below MAX(version), so this migration shipped as
|
|
6
|
+
-- 043 in core 2.1.0 and silently never applied anywhere the retired chain
|
|
7
|
+
-- had run. New core migrations must number ABOVE that ceiling (60) - the
|
|
8
|
+
-- migration-chain test pins the jump so nobody "fixes" the gap back into
|
|
9
|
+
-- the dead zone.
|
|
2
10
|
--
|
|
3
11
|
-- The failure choke already emits a structured code (envelope_missing,
|
|
4
12
|
-- context_compile_scope_denied, ...) and the sanitizer explicitly preserves
|