chore: update package names and versions for consistency

[yu-iskw]

User description

chore: update package names and versions for consistency

• Changed package names from '@coding-agent-fabric/' to 'coding-agent-fabric-' in documentation and code for uniformity.
• Updated version of 'coding-agent-fabric' from 0.1.0 to 0.1.1.
• Added publish configuration to several package.json files to set access to public.
• Corrected README and documentation references to reflect the new package naming convention.

---

PR Type

Enhancement, Documentation

---

Description

• Update package naming convention from scoped to flat format

• Add publishConfig with public access to all packages

• Bump root package version from 0.1.0 to 0.1.1

• Update documentation and code references to reflect naming changes

---

Diagram Walkthrough

flowchart LR
  A["Scoped Package Names<br/>@coding-agent-fabric/*"] -->|"Rename to"| B["Flat Package Names<br/>coding-agent-fabric-*"]
  C["Missing publishConfig"] -->|"Add to"| D["publishConfig with<br/>access: public"]
  E["Version 0.1.0"] -->|"Bump to"| F["Version 0.1.1"]
  B --> G["Updated Documentation<br/>& Code References"]

Loading

File Walkthrough

	Relevant files
Configuration changes	9 files package.json Bump root package version to 0.1.1                                              +1/-1      package.json Add publishConfig with public access                                          +3/-0      package.json Add publishConfig with public access                                          +3/-0      package.json Add publishConfig with public access                                          +3/-0      package.json Add publishConfig with public access                                          +3/-0      package.json Add publishConfig with public access                                          +3/-0      package.json Add publishConfig with public access                                          +3/-0      package.json Add publishConfig with public access                                          +3/-0      publish.yml Set npm scope to coding-agent-fabric                                          +1/-1
Documentation	8 files index.ts Update JSDoc package name reference                                            +1/-1      README.md Update package name in documentation                                          +3/-3      README.md Update package references to flat naming                                  +6/-6      index.ts Update JSDoc package name reference                                            +1/-1      README.md Update package references to flat naming                                  +8/-8      CONTRIBUTING.md Update package names in documentation                                        +3/-3      architecture-revision-core-vs-plugins.md Update plugin names to flat format                                              +2/-2      design_docs.md Update plugin references to flat naming                                    +3/-3
Enhancement	1 files constants.ts Update gemini plugin name to flat format                                  +1/-1

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
⚪	Typosquatting risk Description: Documentation changes introduce the misspelled package name @coding-agent-fablic/cli (and coding-agent-fablic elsewhere), which creates a realistic typosquatting/install-confusion risk where users could install a malicious third-party package matching the typo. README.md [1-9] Referred Code # @coding-agent-fablic/cli Command-line interface for coding-agent-fablic. ## Installation ```bash npm install -g @coding-agent-fablic/cli </details></details></td></tr> <tr><td><details><summary><strong>Unintended public publish </strong></summary><br> <b>Description:</b> Adding <code>publishConfig.access: public</code> across multiple packages can unintentionally publish <br>previously-internal packages to the public npm registry, increasing supply-chain exposure <br>(public availability, wider consumption, and easier targeting) if publication was not <br>intended.<br> <strong><a href='https://github.com/yu-iskw/coding-agent-fabric/pull/12/files#diff-6e2e2a1851648938b325ba84de634407a4e69a644ea61102df15ca4a8a7a9758R49-R52'>package.json [49-52]</a></strong><br> <details open><summary>Referred Code</summary> ```json }, "publishConfig": { "access": "public" }
	Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
🔴	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Misspelled package name: The new documentation/header identifiers introduce an inconsistent and misspelled name (coding-agent-fablic), reducing clarity and making the code/docs misleading relative to the intended coding-agent-fabric naming. Referred Code /** * coding-agent-fablic-plugin-api * * Plugin API and base interfaces for coding-agent-fabric resource handlers Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	✅ Fix recurring typo in package name Suggestion Impact: Updated the CLI README header, description, and npm install command to use "@coding-agent-fabric/cli" instead of the misspelled "@coding-agent-fablic/cli". code diff: -# @coding-agent-fablic/cli +# @coding-agent-fabric/cli -Command-line interface for coding-agent-fablic. +Command-line interface for coding-agent-fabric. ## Installation ```bash -npm install -g @coding-agent-fablic/cli +npm install -g @coding-agent-fabric/cli Correct the recurring typo "fablic" to "fabric" in the package name and description to prevent installation failures. packages/cli/README.md [1-9] -# @coding-agent-fablic/cli +# @coding-agent-fabric/cli -Command-line interface for coding-agent-fablic. +Command-line interface for coding-agent-fabric. ## Installation ```bash -npm install -g @coding-agent-fablic/cli +npm install -g @coding-agent-fabric/cli `[Suggestion processed]` <details><summary>Suggestion importance[1-10]: 8</summary> __ Why: The suggestion correctly identifies a significant typo "fablic" introduced in the PR, which would cause installation and usage issues. </details></details></td><td align=center>Medium </td></tr><tr><td rowspan=1>General</td> <td> <details><summary>unify plugin IDs naming</summary> ___ **Unify all bundled plugin identifiers to use the unscoped <br><code>coding-agent-fabric-plugin-*</code> naming convention for consistency.** [packages/common/src/constants.ts [98-103]](https://github.com/yu-iskw/coding-agent-fabric/pull/12/files#diff-4fd68e2c63d31c2a8b89894bc59d6cc1f9041a7aadca973afdc1489e0e14d86eR98-R103) ```diff export const BUNDLED_PLUGINS = [ - '@coding-agent-fabric/plugin-claude-code-hooks', - '@coding-agent-fabric/plugin-cursor-hooks', + 'coding-agent-fabric-plugin-claude-code-hooks', + 'coding-agent-fabric-plugin-cursor-hooks', 'coding-agent-fabric-plugin-gemini-cli-hooks', - '@coding-agent-fabric/plugin-mcp', + 'coding-agent-fabric-plugin-mcp', ] as const; Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly points out an inconsistency in plugin naming within the BUNDLED_PLUGINS array and proposes a fix that aligns with the PR's goal of using an unscoped naming convention.	Medium
Update