{"version":"2.1.229","anchor":"command-sourced-plugins-record-where-their-files-came-from","canonical_anchor":"command-sourced-plugins-record-where-their-files-came-from","heading":"Command-sourced plugins record where their files came from","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/command-sourced-plugins-record-where-their-files-came-from","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Command-sourced plugins record where their files came from\n\nCommand-built plugins record their command and output directory so moves can be detected.\n\n**What**\n\nInstalls of plugins that build themselves by running a command now store the command, the directory it produced and any previous producer directories, so a later change of location can be spotted. Reinstalling from cache now fails with a distinct \"not cached\" code instead of a generic \"not found\".\n\n**Details**\n\n- Installs pass a consent record of `shown`, `recorded` or `none`.\n- Plugin state tracks which producer directories have been scanned and which were denied.\n\n**Evidence**\n\n`failureCode: r ? \"not_cached\" : \"not_found\"`\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}