Files Changed: adopt plugin and runner business records

[jeonghun-jj-lee]

Files Changed: adopt plugin and runner business records

Important

Problem - Amicode plugin tools and run creation write problem records, run metadata, and artifacts outside the engine's ordinary file tools. They need provenance without recursively tracking caches, queues, credentials, or ledger infrastructure.
Approach - Classify plugin and runner business resources in the mutator registry, issue declared contexts for them, and explicitly exclude operational state. Contextless CLI or shell launches remain opaque rather than falsely session-owned.
Scope - in: problem records, run metadata, declared artifacts, system-origin receipts, resource classification, and opaque CLI fallback. out: engine tools, app editing, and full UI aggregation.
Assumptions - The lineage, ledger, mutation gate, and privacy contracts are available.

Acceptance Criteria

• Registered plugin business writes produce system-origin receipts tied to the initiating session lineage.
• Registered runner metadata and declared artifacts produce receipts with safe evidence or artifact references.
• Credentials, caches, queues, updater state, telemetry, ledger storage, and retention state are explicitly out of scope and cannot recurse into receipts.
• Contextless CLI and shell launches produce an unknown-operation receipt instead of adopting filesystem effects.
• Protected internal values are redacted by the exposure matrix before any display projection.
• Deleting a root applies retention consistently to plugin and runner evidence.

Testing Decisions

• Extend plugin and runner tests for declared contexts, system origins, artifact evidence, redaction, root deletion, and opaque CLI behavior.
• Add registry completeness coverage for all plugin and runner write routes.

Key Decisions

• Business records are visible session work; operational machinery is not.
• Artifact links are preferred over copying large generated outputs into ledger evidence.

Constraints & Invariants

• A run artifact cannot reveal protected internal data through Files Changed.
• Registry classification is required before a new plugin or runner writer ships.

Prior Art

• Parent Files Changed: full session-lineage mutation ledger #972
• Existing problem records and run-artifact contracts

Deliberation Resolution

• A resource is business-visible when it is a durable problem, run, or artifact record referenced by a researcher-facing surface. Credentials, caches, queues, transient staging, updater state, telemetry, ledger infrastructure, and retention transitions are operational.
• A staging resource remains operational until its successful promotion creates the durable business record; failed staging cleanup does not create a business receipt.
• System-origin receipts include root ID, initiating session ID, route ID, operation ID, resource classification, execution outcome, and a display-safe evidence reference. Contextless CLI work emits an Unknown Mutation Receipt with no adopted resources.
• Artifact links are display-safe projections subject to the exposure matrix; opening one reauthorizes against the same root and policy, so a link cannot bypass redaction or retention.

Source

Part of #972. Blocked by #1077 and #1078.