@intoinside/praxis 1.0.1 → 1.0.3

package/package.json

@@ -1,12 +1,15 @@
 {
   "name": "@intoinside/praxis",
-  "version": "1.0.1",
+  "version": "1.0.3",
   "description": "**Praxis** is an intent-first development framework that bridges **Intent‑Driven Development (IDD)** and **Spec‑Driven Development (SDD)** into a single, coherent workflow.",
   "main": "src/index.js",
   "types": "src/index.d.ts",
   "bin": {
     "praxis": "src/index.js"
   },
+  "dependencies": {
+    "commander": "^14.0.2"
+  },
   "scripts": {
     "build": "tsc",
     "prepublishOnly": "npm run build",
@@ -33,7 +36,6 @@
   "homepage": "https://github.com/intoinside/Praxis#readme",
   "devDependencies": {
     "@types/node": "^25.0.10",
-    "commander": "^14.0.2",
     "ts-node": "^10.9.2",
     "typescript": "^5.9.3"
   }

package/CODE_OF_CONDUCT.md

@@ -1,99 +0,0 @@
-# Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic
-status, nationality, personal appearance, race, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our community include:
-
-- Demonstrating empathy and kindness toward other people
-- Being respectful of differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the overall community
-
-Examples of unacceptable behavior include:
-
-- The use of sexualized language or imagery, and sexual attention of any kind
-- Trolling, insulting or derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or email address,
-  without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards
-of acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for
-moderation decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces. Examples
-of representing our community include using an official e-mail address, posting
-via an official social media account, or acting as an appointed representative
-at an online or offline event.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation
-and an explanation of why the behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including
-unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding
-interactions in community spaces as well as external channels like social media. Violating these terms may lead to a
-temporary or permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified
-period of time. No public or private interaction with the people involved, including unsolicited interaction with those
-enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate
-behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq]
-[FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations

package/CONTRIBUTING.md

@@ -1,108 +0,0 @@
-# Contributing to Praxis
-
-Thank you for your interest in contributing to Praxis! We welcome
-contributions from the community to help improve the intent/spec-driven
-development experience.
-
-## Table of Contents
-
-- [Getting Started](#getting-started)
-- [Development Setup](#development-setup)
-- [Contributing Guidelines](#contributing-guidelines)
-- [Adding New Agent Support](#adding-new-agent-support)
-- [Testing](#testing-requirements)
-- [Documentation](#documentation)
-- [Release Process](#release-process)
-- [Community](#community)
-
-## Getting Started
-
-1. **Fork the repository** on GitHub
-2. **Clone your fork** locally:
-
-   ```bash
-   git clone https://github.com/your-username/praxis.git
-   cd praxis
-   ```
-
-3. **Set up the development environment** (see [Development Setup](#development-setup))
-4. **Create a feature branch**:
-
-   ```bash
-   git checkout -b feature/your-feature-name
-   ```
-
-5. **Make your changes** and ensure tests pass
-6. **Submit a pull request** with a clear description of your changes
-
-## Development Setup
-
-### Prerequisites
-
-- **Git**
-- **Supported AI agent** (for testing)
-
-## Contributing Guidelines
-
-### Code Standards
-
-- **Follow PEP 8** for Python code style
-- **Use type hints** for all function signatures
-- **Write docstrings** for all public functions and classes
-- **Keep functions small** and focused on single responsibilities
-- **Use meaningful variable names** and avoid abbreviations
-
-### Commit Guidelines
-
-- **Use conventional commits**: `feat:`, `fix:`, `docs:`, `style:`, `refactor:`, `test:`, `chore:`
-- **Write clear commit messages** explaining what and why
-- **Reference issues** when applicable: `Fixes #123`, `Closes #456`
-- **Keep commits atomic** - one logical change per commit
-
-### Pull Request Process
-
-1. **Update documentation** if you're changing functionality
-2. **Add tests** for new features or bug fixes
-3. **Submit your PR** with a clear description
-
-### Testing Requirements
-
-- **Unit tests** for all new functionality
-- **Integration tests** for CLI commands and agent interactions
-- **Cross-platform tests** (Windows, macOS, Linux)
-- **Agent compatibility tests** for all supported AI agents
-
-## Documentation
-
-### Documentation Structure
-
-- **`README.md`**: Main project overview and getting started guide
-- **Inline documentation**: Code comments and docstrings
-
-### Writing Documentation
-
-- **Use clear, concise language** appropriate for the audience
-- **Include examples** for complex features
-- **Keep documentation in sync** with code changes
-- **Use relative links** for internal references
-- **Test code examples** to ensure they work
-
-## Community
-
-### Getting Help
-
-- **GitHub Issues**: For bug reports and feature requests
-- **GitHub Discussions**: For questions and discussions
-- **Documentation**: Check the docs first for common questions
-
-### Code of Conduct
-
-Please read and follow our [Code of Conduct](./CODE_OF_CONDUCT.md) when participating in the Praxis community.
-
-### Recognition
-
-Contributors who make significant improvements to Praxis may be recognized in the project documentation or release notes.
-
----
-
-Thank you for contributing! Your help makes Praxis better for everyone.

package/MAINTAINERS.md

@@ -1,9 +0,0 @@
-# Maintainers
-
-People who maintain and guide Praxis.
-
-## Core Maintainers
-
-| Name | GitHub | Role |
-|------|--------|------|
-| Raffaele Intorcia | [@intoinside](https://github.com/intoinside) | Lead maintainer |

package/last_error.txt

@@ -1,42 +0,0 @@
-node : (node:14940) ExperimentalWarning: 
-`--experimental-loader` may be removed 
-in the future; instead use `register()`:
-In riga:1 car:1
-+ node --loader ts-node/esm src/index.ts 
---help 2>&1 | Out-File -FilePa ...
-+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-~~~~~~~~~~~
-    + CategoryInfo          : NotSpecifi 
-   ed: ((node:14940) Ex...e `register()  
-  `::String) [], RemoteException
-    + FullyQualifiedErrorId : NativeComm 
-   andError
- 
---import 'data:text/javascript,import { 
-register } from "node:module"; import { 
-pathToFileURL } from "node:url"; 
-register("ts-node/esm", 
-pathToFileURL("./"));'
-(Use `node --trace-warnings ...` to show 
-where the warning was created)
-(node:14940) [DEP0180] 
-DeprecationWarning: fs.Stats constructor 
-is deprecated.
-(Use `node --trace-deprecation ...` to 
-show where the warning was created)
-Usage: praxis [options] [command]
-
-Praxis: Intent-First Development Framework
-
-Options:
-  -V, --version    output the version number
-  -h, --help       display help for command
-
-Commands:
-  init             Initialize a new project to be used with Praxis
-  intent           Manage intents (the WHY)
-  model [options]  Generate or update the intent model
-  spec             Manage specifications (the WHAT)
-  analyze          Analyze impact and drift
-  integration      IDE and AI integration
-  help [command]   display help for command