instar 1.3.880 → 1.3.881

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "instar",
-  "version": "1.3.880",
+  "version": "1.3.881",
   "description": "Coherence infrastructure for self-evolving AI agents — on the Claude Code or Codex subscription you already have.",
   "type": "module",
   "main": "dist/index.js",

package/src/data/builtin-manifest.json

@@ -1,8 +1,8 @@
 {
   "$schema": "./builtin-manifest.schema.json",
   "schemaVersion": 1,
-  "generatedAt": "2026-07-19T11:44:57.289Z",
-  "instarVersion": "1.3.880",
+  "generatedAt": "2026-07-19T13:38:17.474Z",
+  "instarVersion": "1.3.881",
   "entryCount": 202,
   "entries": {
     "hook:session-start": {

package/upgrades/1.3.881.md

@@ -0,0 +1,23 @@
+# Upgrade Guide — vNEXT
+
+<!-- assembled-by: assemble-next-md -->
+<!-- bump: patch -->
+
+## What Changed
+
+- Added the canonical WS3–WS4 Slack apprenticeship retrospective with attributed defects and durable lessons.
+- Added a non-executing WS5 scope stub for the future demo-channel responding rung, including preconditions, operator-only enforcement authority, rollback, and the required test matrix.
+
+## What to Tell Your User
+
+The Slack demo work is now consolidated into one durable retrospective: what succeeded, what failed, who caught each defect, and the rules those incidents earned. It also defines the next responding-mode rung without enabling it; the operator retains the decision to grant real speaking authority.
+
+## Summary of New Capabilities
+
+- No runtime capability is enabled by this documentation PR.
+- A future WS5 build now has an explicit acceptance matrix and operator-only enforcement boundary.
+
+## Evidence
+
+- `docs/apprenticeship/slack-workstream-retro.md`
+- PR #1518 (merge `4f80badcee8e72fd10a4ced155352aeba907199e`) and feedback entries `fb-b1010093-9db`, `fb-d54eb6d4-8d2`

package/upgrades/side-effects/slack-workstream-retro.md

@@ -0,0 +1,45 @@
+# Side-effects review: Slack workstream retrospective and WS5 scope
+
+This is a documentation-only change. It changes no runtime, configuration, credentials, Slack state, or enforcement posture.
+
+## Over-block
+
+None at runtime. The scope intentionally states that observe-to-respond requires an operator decision; this documents the existing authority boundary rather than adding a gate.
+
+## Under-block
+
+The WS5 matrix is a design stub, not executable enforcement. A future implementation must earn each assertion and must not cite this document as permission to flip responding on.
+
+## Level-of-abstraction fit
+
+The apprenticeship retrospective belongs under `docs/apprenticeship/`: it preserves attributed program evidence and converts incidents into reusable development constraints. The forward scope is colocated so the next increment starts from the earned evidence rather than chat archaeology.
+
+## Signal vs authority compliance
+
+The document explicitly separates readiness signals from the operator's authority to move the adapter from observe-only to responding. No detector or model verdict is granted authority.
+
+## Interactions
+
+No runtime interaction. The prose aligns the Slack reprovision runbook, PR #1518's source-bound relay, owned-identity self-unblock posture, and existing operator-only enforcement principle.
+
+## External surfaces
+
+The document is repository-visible. It contains non-secret identifiers only as issue/PR references and no Slack credentials, tokens, private message text, or raw user identifiers.
+
+## Multi-machine posture
+
+The scope requires owner-local refusal, durable custody, and exactly one speaking machine. This review makes no claim that those future cells are already implemented.
+
+## Rollback cost
+
+Documentation-only revert. No data or external-state repair would be required.
+
+## Operator-surface quality
+
+The future decision surface is specified to show exact scope, evidence freshness, known gaps, and rollback. No operator UI is added here.
+
+## Conclusion
+
+The retrospective is an honest consolidation of completed evidence, and the WS5 section is explicitly non-executing. No side-effect concern blocks publication.
+
+The operator-authority boundary remains unchanged by this documentation.

package/upgrades/slack-workstream-retro.eli16.md

@@ -0,0 +1,11 @@
+# Slack workstream retrospective and WS5 scope — plain-English overview
+
+This change records what Instar-codey and Echo learned while bringing a dedicated demo Slack app from provisioning through a real end-to-end conversation path. It does not turn on any new Slack behavior. The retrospective captures the successful pieces—distinct app identity, verified permissions and channel membership, live inbound events, thread routing, and the source-bound reply relay shipped in PR #1518—and it names the failures that made those contracts necessary.
+
+The most important lesson is that several green-looking signals are narrower than they appear. A connected Socket Mode WebSocket does not prove that Slack event subscriptions survived an app update. A manifest write does not prove a bot token gained the intended scopes. A plausible credential file does not replace a signed or owner-issued identity attestation. And a spawned session does not need arbitrary channel coordinates; it needs a narrowly bound way to answer the conversation that created it.
+
+The document also scopes the next Slack increment without building it. Today the demo adapter observes and records decisions but does not autonomously speak. WS5 would prove a real authorized human can direct the agent in a demo channel and receive one useful, thread-correct response. That observe-to-respond transition is a genuine authority change. Tests and reviewers can show readiness, but only the operator may enable it. The proposed matrix covers authorized and unauthorized senders, ambient traffic, duplicates, recovery, cross-machine owner-dark behavior, one-voice delivery, rollback, migration parity, and cleanup.
+
+The decision this document enables is simple: whether to authorize a future build of WS5 under those boundaries. This PR itself makes no configuration change, touches no Slack workspace, and grants no speaking authority.
+
+Readers should treat the proposed matrix as a future acceptance contract, never as evidence that respond mode is already ready or enabled.