vibe64 0.1.31 → 0.1.33
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/bin/upgrade-state.js +5057 -5043
- package/docs/colleague-usage/colleague-upgrade-recovery.md +11 -0
- package/package.json +1 -1
|
@@ -24,3 +24,14 @@ old action to manufacture a completion receipt.
|
|
|
24
24
|
The same recovery applies on desktop and mobile. Colleague can explain the error
|
|
25
25
|
and guide you to the available application controls, but this maintenance requires
|
|
26
26
|
the operator's interaction and cannot be executed through Colleague actions.
|
|
27
|
+
|
|
28
|
+
An older interactive chat may also use a native input format from before the
|
|
29
|
+
application recorded its autonomous flag. The operator can apply the separate
|
|
30
|
+
qualified historical correction after checking the exact original native input,
|
|
31
|
+
completed answer and account/scope custody. It preserves the chat and its native
|
|
32
|
+
identity. A missing flag by itself is not permission to resume or resend anything;
|
|
33
|
+
unsupported or uncertain native evidence still prevents activation.
|
|
34
|
+
|
|
35
|
+
Current chat formats continue through their original migration; the historical
|
|
36
|
+
correction leaves them unchanged. A continuity error still requires the operator
|
|
37
|
+
to inspect its exact evidence before activation.
|