instar 1.3.1000 → 1.3.1001
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/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "./builtin-manifest.schema.json",
|
|
3
3
|
"schemaVersion": 1,
|
|
4
|
-
"generatedAt": "2026-07-
|
|
5
|
-
"instarVersion": "1.3.
|
|
4
|
+
"generatedAt": "2026-07-27T10:24:33.892Z",
|
|
5
|
+
"instarVersion": "1.3.1001",
|
|
6
6
|
"entryCount": 202,
|
|
7
7
|
"entries": {
|
|
8
8
|
"hook:session-start": {
|
|
@@ -0,0 +1,48 @@
|
|
|
1
|
+
# Upgrade Guide — vNEXT
|
|
2
|
+
|
|
3
|
+
<!-- assembled-by: assemble-next-md -->
|
|
4
|
+
<!-- bump: patch -->
|
|
5
|
+
|
|
6
|
+
## What Changed
|
|
7
|
+
|
|
8
|
+
Adds `docs/specs/decision-replayability-standard.md` (plus its ELI16 companion) — the written
|
|
9
|
+
standard for what must be recorded so a decision can be replayed and re-evaluated later, rather than
|
|
10
|
+
merely asserted to have happened.
|
|
11
|
+
|
|
12
|
+
It answers the question the operator asked directly: **is a screenshot an acceptable thing to store?**
|
|
13
|
+
For a TERMINAL prompt the answer is no, and not for privacy reasons — the scrubbed pane TEXT of the
|
|
14
|
+
prompt region carries identical information to an image of it, but only text is scrubbable,
|
|
15
|
+
greppable, and diffable. Text is therefore *more* auditable, not less. Images remain the right medium
|
|
16
|
+
only where no text form exists, such as a GUI or a browser.
|
|
17
|
+
|
|
18
|
+
The standard carries three bounds so the rule cannot quietly become unbounded surveillance: capture
|
|
19
|
+
the prompt REGION rather than full scrollback; scrub before write, never after; and mark a record
|
|
20
|
+
`replayability: degraded` when scrubbing has hollowed it out, so a log can never silently become
|
|
21
|
+
useless while still looking complete.
|
|
22
|
+
|
|
23
|
+
## What to Tell Your User
|
|
24
|
+
|
|
25
|
+
None — internal change (no user-facing surface).
|
|
26
|
+
|
|
27
|
+
## Summary of New Capabilities
|
|
28
|
+
|
|
29
|
+
None — internal change (no user-facing surface).
|
|
30
|
+
|
|
31
|
+
## Evidence
|
|
32
|
+
|
|
33
|
+
Docs-only: no runtime surface, no endpoint, no config key, no behaviour change. The standard's own
|
|
34
|
+
`## Decision points touched` and `## Multi-machine posture` sections are present as the spec format
|
|
35
|
+
requires.
|
|
36
|
+
|
|
37
|
+
Shipped as its own change deliberately. The document was written and staged inside an unrelated
|
|
38
|
+
worktree that is blocked awaiting operator approval — so a finished deliverable was sitting
|
|
39
|
+
uncommitted behind a blocker it has no dependency on, one worktree removal away from being lost.
|
|
40
|
+
Extracting it is the concrete application of the project's own rule that deferral is deletion.
|
|
41
|
+
|
|
42
|
+
## Known limits
|
|
43
|
+
|
|
44
|
+
This ships the standard, not its enforcement. Applying it to the first runtime consumer
|
|
45
|
+
(`PermissionPromptAutoResolver`, which today records matched-pattern names and a one-way fingerprint
|
|
46
|
+
but no replayable prompt region) is tracked separately as ACT-1312 and is deliberately NOT bundled
|
|
47
|
+
here. Until that lands, the standard is a written rule with no mechanical guard behind it — which by
|
|
48
|
+
this project's own measure means it is not yet enforced.
|