From 99bc4990bdb0ea74cb50d8f8468658b375c544af Mon Sep 17 00:00:00 2001
From: David Snelling <david@soulcraft.com>
Date: Fri, 23 May 2025 11:30:19 -0700
Subject: [PATCH] Set package.json private flag to false for npm publication

Changed `"private"` to `false` in package.json to allow publishing the package to npm. The `"access": "restricted"` setting ensures that access remains limited to @soulcraft organization members. Updated README to reflect the new configuration.
---
 README.md    | 4 ++--
 package.json | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 41955cf9..38b086e5 100644
--- a/README.md
+++ b/README.md
@@ -135,13 +135,13 @@ To publish updates to the package:
 
 Note that the package has the following configuration in package.json:
 ```json
-"private": true,
+"private": false,
 "publishConfig": {
   "access": "restricted"
 }
 ```
 
-This ensures that the package is only accessible to users with appropriate permissions within the @soulcraft organization.
+This ensures that the package is only accessible to users with appropriate permissions within the @soulcraft organization. The `"access": "restricted"` setting limits access to the package to members of the @soulcraft organization, while `"private": false` allows the package to be published to npm.
 
 ### Installing the Private Package
 
diff --git a/package.json b/package.json
index 9e576c3e..e959c05c 100644
--- a/package.json
+++ b/package.json
@@ -30,7 +30,7 @@
   ],
   "author": "David Snelling (david@soulcraft.com)",
   "license": "MIT",
-  "private": true,
+  "private": false,
   "publishConfig": {
     "access": "restricted"
   },