feat(chore): added git templates

added git templates

Gh-1

Author: vaibhavbhalla2505

.cz-config.js

@@ -44,7 +44,7 @@ module.exports = {
     // used if allowCustomScopes is true
     customScope: 'Denote the SCOPE of this change:',
     subject: 'Write a SHORT, IMPERATIVE tense description of the change:\n',
-    body: 'Provide a LONGER description of the change (mandatory). Use "\\n" to break new line:\n',
+    body: 'Provide a LONGER description of the change (optional). Use "|" to break new line:\n',
     breaking: 'List any BREAKING CHANGES (optional):\n',
     footer: 'List any ISSUES CLOSED by this change (optional). E.g.: GH-144:\n',
     confirmCommit: 'Are you sure you want to proceed with the commit above?',

.eslintignore

@@ -2,3 +2,5 @@ node_modules/
 dist/
 coverage/
 .eslintrc.js
+.cz-config.js
+commitlint.config.js

.github/workflows/release.yaml

@@ -32,7 +32,7 @@ jobs:
         run: |
           git config --global user.name $CONFIG_USERNAME
           git config --global user.email $CONFIG_EMAIL
-          git remote set-url origin https://$GITHUB_ACTOR:[email protected]/sourcefuse/loopback4-authorization
+          git remote set-url origin https://$GITHUB_ACTOR:[email protected]/sourcefuse/loopback4-mcp
         env:
           GITHUB_PAT: ${{ secrets.RELEASE_COMMIT_GH_PAT }}
           CONFIG_USERNAME: ${{ vars.RELEASE_COMMIT_USERNAME }}

.github/workflows/sync-docs.yaml

@@ -50,7 +50,7 @@ jobs:
           git checkout -B $extension_branch || git checkout $extension_branch
 
           # Copy README from the extension repo
-          cp ../extension/docs/README.md docs/arc-api-docs/extensions/$(basename $GITHUB_REPOSITORY)/
+          cp ../extension/README.md docs/arc-api-docs/extensions/$(basename $GITHUB_REPOSITORY)/
           git add .
 
           if git diff --quiet --cached; then

.vscode/settings.json

@@ -15,7 +15,7 @@
     "**/.hg": true,
     "**/.svn": true,
     "**/CVS": true,
-    "dist": true,
+    "dist": false,
   },
   "files.insertFinalNewline": true,
   "files.trimTrailingWhitespace": true,

README.md

@@ -20,7 +20,7 @@ Its purpose is to enable LoopBack APIs, services, and business logic to be expos
 
 - Lifecycle-managed Tool Registry :-
   A dedicated `McpToolRegistry` service maintains all discovered tool metadata,their handlers and execution context.
-  
+
   A `McpToolRegistryBootObserver` ensures that registration happens only after the application has fully booted.
 ## Installation
 ```sh
@@ -45,8 +45,14 @@ async createUser(args: {email: string; name: string}) {
   return {message: `User ${args.name} created`};
 }
 ```
+
+This decorator accepts a total of five fields, out of which `name` and `description` are mandatory and `schema`,`preHook` and `postHook` are optional enhancements.
+
+The schema field allows defining a Zod-based validation schema for tool input parameters, while preHook and postHook enable execution of custom logic before and after the tool handler runs.
+
 ### Mcp Hook Usage Details
   To use hooks with MCP tools, follow the provider-based approach:
+
   Step 1: Create a hook provider:
   ```typescript
   // src/providers/my-hook.provider.ts