citadel_cli 1.1.5 → 1.1.7

package/README.md

@@ -151,79 +151,4 @@ Then to make the component aware of them:
 
 ## Contributing
 
-Contributions are welcome.
-
-1. Clone the repository:
-```bash
-git clone https://github.com/jchilders/citadel_cli.git
-cd citadel_cli
-```
-
-2. Install dependencies:
-```bash
-npm install
-```
-
-3. Build the package:
-```bash
-npm run build
-```
-
-4. (Optional but recommended) Link citadel so you can import it into a parallel project
-```bash
-npm link
-```
-
-5. (Optional) From the directory of the project you want to import Citadel into:
-```bash
-npm unlink citadel_cli && npm link citadel_cli
-# ... your normal dev process ...
-```
-
-Load your appliation and press <kbd>.</kbd>
-
-### Bug Reports and Feature Requests
-
-- Use the GitHub Issues section to report bugs or suggest features
-- Before creating a new issue, please check if a similar issue already exists
-- Provide as much detail as possible in bug reports:
-  - Steps to reproduce the issue
-  - Expected behavior
-  - Actual behavior
-  - Browser/environment information
-  - Error messages or screenshots if applicable
-
-### Development Process
-
-1. Fork the repository
-2. Create a new branch for your feature or bugfix:
-   ```bash
-   git checkout -b feature/your-feature-name
-   # or
-   git checkout -b fix/your-bugfix-name
-   ```
-3. Make your changes
-4. Write or update tests as needed
-5. Run the test suite to ensure everything passes:
-   ```bash
-   npm run test
-   ```
-6. Commit your changes with a clear and descriptive commit message
-7. Push to your fork and submit a pull request
-
-### Pull Request Guidelines
-
-- Keep your changes focused. Submit separate pull requests for separate features/fixes
-- Follow the existing code style and conventions
-- Include tests for new functionality
-- Update documentation as needed
-- Ensure all tests pass
-- Describe your changes in detail in the pull request description
-
-### Code Style
-
-- Follow TypeScript best practices
-- Use meaningful variable and function names
-- Comment complex logic or non-obvious code
-- Keep functions focused and modular
-- Use consistent formatting (the project uses ESLint and Prettier)
+See [CONTRIBUTING.md](./CONTRIBUTING.md) for guidelines on developing, testing, and releasing Citadel CLI.

package/dist/App.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/__test-utils__/factories.d.ts

@@ -25,8 +25,6 @@ export declare const setupCitadelStateHook: () => {
     hook: import('@testing-library/react').RenderHookResult<{
         state: CitadelState;
         actions: CitadelActions;
-        getAvailableCommands_s: () => string[];
-        getAvailableCommandSegments: () => CommandSegment[];
     }, unknown>;
     mockHistory: CommandHistory;
     mockActions: CommandHistoryActions;