Fix binary name conflict with zero-to-prod-data-model-factory (#35)

* Add implementation plan for binary name conflict resolution

* Remove conflicting binary zero-to-prod-data-model-factory

* Remove conflicting binary from composer.json bin array

* Add context directory to export-ignore

Author: zero-to-prod

.gitattributes

@@ -12,4 +12,5 @@
 /SECURITY.md              export-ignore
 /test.sh                  export-ignore
 /dock                     export-ignore
-/art/                     export-ignore
+/art/                     export-ignore
+/context/                 export-ignore

bin/zero-to-prod-data-model-factory

@@ -51,7 +51,6 @@
         "phpunit/phpunit": "<12.0"
     },
     "bin": [
-        "bin/zero-to-prod-data-model-factory",
         "bin/zero-to-prod-data-model-helper"
     ],
     "suggest": {

composer.json

@@ -0,0 +1,31 @@
+# Name conflicts with an existing file
+
+**Issue #32** | **State:** OPEN | **Created:** 2025-09-02T21:37:24Z
+
+**Labels:** None  
+**Assignees:** None
+
+**GitHub URL:** https://github.com/zero-to-prod/data-model-helper/issues/32
+
+## Description
+
+**Describe the bug**
+When installing this package I see this error:
+```shell
+Skipped installation of bin bin/zero-to-prod-data-model-factory for package zero-to-prod/data-model-helper: name conflicts with an existing file
+```
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Update this package in an existing project with this in `composer.json`
+```json
+    "post-update-cmd": [
+      "zero-to-prod-package-helper"
+    ],
+```
+2. Run: `composer update`
+5. See error: `Skipped installation of bin bin/zero-to-prod-data-model-factory for package zero-to-prod/data-model-helper: name conflicts with an existing file`
+
+**Expected behavior**
+Remove confict.

context/issues/32-name-conflicts-with-an-existing-file.md

@@ -0,0 +1,44 @@
+# Implementation Plan: Resolve Binary Name Conflict (Issue #32)
+
+## Context
+Reference: [context/issues/32-name-conflicts-with-an-existing-file.md](../issues/32-name-conflicts-with-an-existing-file.md)
+
+## Problem
+When installing the `zero-to-prod/data-model-helper` package, Composer reports a binary name conflict:
+```
+Skipped installation of bin bin/zero-to-prod-data-model-factory for package zero-to-prod/data-model-helper: name conflicts with an existing file
+```
+
+## Root Cause Analysis
+The package includes `bin/zero-to-prod-data-model-factory` in its bin array, but this conflicts with another package or existing binary file in the user's environment.
+
+## Solution Strategy
+Remove the conflicting binary from the package configuration since:
+1. The main functionality should be provided by `bin/zero-to-prod-data-model-helper`
+2. The `zero-to-prod-data-model-factory` binary may be provided by a separate package (`zero-to-prod/data-model-factory`)
+3. The conflict prevents proper installation
+
+## Implementation Steps
+
+### 1. Update composer.json
+- Remove `bin/zero-to-prod-data-model-factory` from the bin array
+- Keep only `bin/zero-to-prod-data-model-helper` as the main binary
+- This maintains the core functionality while resolving the conflict
+
+### 2. Remove conflicting binary file
+- Delete the `bin/zero-to-prod-data-model-factory` file from the repository
+- This prevents future conflicts and clarifies package responsibility
+
+### 3. Update package suggestions
+- Ensure `zero-to-prod/data-model-factory` is properly suggested in composer.json
+- This guides users to the correct package for factory functionality
+
+## Expected Outcome
+- Composer installation will complete without conflicts
+- Users can still access factory functionality via the dedicated `zero-to-prod/data-model-factory` package
+- Package installation integrates properly with `post-update-cmd` scripts
+
+## Validation
+- Test composer installation in a clean environment
+- Verify the remaining binary (`zero-to-prod-data-model-helper`) functions correctly
+- Confirm no regression in core package functionality