{"version":"2.1.236","anchor":"specific-reasons-when-an-artifact-write-approval-does-not-ma","canonical_anchor":"specific-reasons-when-an-artifact-write-approval-does-not-ma","heading":"Specific reasons when an artifact write approval does not match the file","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/specific-reasons-when-an-artifact-write-approval-does-not-ma","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Specific reasons when an artifact write approval does not match the file\n\nFailed artifact file approvals now name the reason and the fix instead of generic denial text.\n\n**What**\n\nWhen approving a file for an artifact fails, you now get a named reason and what to do about it instead of generic denial text.\n\n**Details**\n\n- Reasons distinguish the file changing since approval, reaching the file through a symbolic link, a hard link, a read that would need permission, no identity, the path not being a regular file, and size.\n- Each carries remediation, such as passing the resolved path or copying the file under the working directory.\n- The symlink, hard-link and size checks now live in one shared helper rather than being repeated per action.\n\n**Evidence**\n\n`file_path reaches its file through a symbolic link that resolves somewhere this session may not read without asking`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}