Repository navigation
Require production evidence before adoption - #77
Conversation
Keep packaged resources, accepted owner amendments and actual child outcomes tied to the delivered artifact. Preserve native acceptance as a separate condition. Refs #76. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
|
Delivered as Factory 0.1.18. The remote tag and all 45 published source files match the reviewed merge; required PR and main checks passed. The three changed skills were reconciled into the two existing Codex/Claude skill locations: 18 selected files verified, both prior copies retained for recovery. A fresh Codex context explicitly read the new guidance and held the incomplete-package example. Automatic discovery/invocation and fresh Claude loading are not claimed. This completes the method delivery, not product acceptance. Latest lead readback: AIOS has owner icon PASS plus native opening/Settings evidence, and #56 is closed. OPD’s owner chose one localhost web editor; its same writer is completing that direct workflow and shared-canvas agent editing. #76 retains that follow-through; a dedicated MCP panel is optional. No runtime, permissions, credentials or product source changed. |
OPD’s handoff allowed adoption after passing tests even though the production build lacked two editor assets. AIOS’s contrast brief also dropped an accepted geometry change. This fixes those specific gaps in the existing skills.
Before: tests used a substitute asset list, and production smoke was optional before installation. After: applicable proof from the exact production artifact must pass before adoption. Missing proof holds installation. The lead also carries accepted owner amendments into writer/review criteria and reconciles actual child results before reporting completion.
Checks and review:
editor.jsandpanel.js; the complete replacement passes membership and receipt checks. This is offline historical evidence, not a new native run or a cache diagnosis.Product-native acceptance remains with the existing project leads; this method change does not itself prove a plugin workflow or appearance. See #76 for current product readbacks. Native acceptance after authorized installation stays separate. No product source, runtime or permissions changed.
Refs #76.