fix: configure storage-construct package for proper changeset versioning

- Set initial version to 0.1.0 for new package (changeset will bump to 1.0.0)
- Add storage-construct to version check exceptions for 0.x.x versions
- Update changeset description to reflect initial release rather than breaking change
- Update package-lock.json with corrected version
- Fix husky hooks with proper PATH configuration

Author: rozaychen

.changeset/grumpy-icons-lie.md

@@ -2,10 +2,11 @@
 '@aws-amplify/storage-construct': major
 ---
 
-Breaking change: Add grantAccess method pattern to AmplifyStorage construct
+Initial release of standalone AmplifyStorage construct package
 
-- Replace constructor-based access control with method-based pattern
-- Add `grantAccess(auth, accessDefinition)` method for post-construction access control
+- Create new `@aws-amplify/storage-construct` as standalone CDK L3 construct
+- Migrate AmplifyStorage implementation with CDK-native triggers
+- Add `grantAccess(auth, accessDefinition)` method for access control
 - Add `StorageAccessDefinition` type for structured access configuration
-- Remove access prop from constructor (breaking change)
-- Maintain all existing S3 bucket functionality
+- Support all S3 bucket features (CORS, versioning, SSL enforcement, auto-delete)
+- Provide comprehensive TypeScript declarations and API documentation

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@aws-amplify/storage-construct",
-  "version": "1.0.0",
+  "version": "0.1.0",
   "type": "module",
   "publishConfig": {
     "access": "public"

packages/storage-construct/package.json

@@ -11,6 +11,7 @@ const packagePaths = await glob('./packages/*');
 const getExpectedMajorVersion = (packageName: string) => {
   switch (packageName) {
     case 'ampx':
+    case '@aws-amplify/storage-construct':
       return '0.';
     case '@aws-amplify/backend-deployer':
     case '@aws-amplify/cli-core':