Remove deprecated files and update project structure for improved clarity (#21)

- Deleted `llms.txt`, `examples/code-deployment.js`, `examples/code-deployment.ts`, and other related deployment utilities to streamline the SDK.
- Updated `package.json` to reflect changes in type definitions and removed references to deprecated modules.
- Refactored `README.md` to remove outdated documentation and clarify breaking changes in version 0.5.8.
- Adjusted TypeScript configuration and logging utilities for better performance and maintainability.
- Enhanced error handling in various services and methods to improve robustness.

Author: EditUndo

README.md

@@ -18,7 +18,6 @@ This SDK leverages a service-oriented architecture for building AI agents allowi
   - [Features](#features)
   - [Installation](#installation)
   - [Requirements](#requirements)
-  - [Documentation](#documentation)
   - [Example](#example)
   - [Running Tests](#running-tests)
   - [Usage](#usage)
@@ -38,6 +37,15 @@ This SDK leverages a service-oriented architecture for building AI agents allowi
   - [License](#license)
   - [Acknowledgements](#acknowledgements)
 
+**Breaking Changes in v0.5.8**
+- Pino has been removed and replaced with console for better portability and is set to silent by default. 
+- The default handler for streamMessage no longer automatically emits an initial `submitted` and `working` event.
+- Agent Registration, Bundling and Deployment utils have been removed (email us: humans@artinet.io for support).
+- `@artinet/metadata-validator` has been removed due to build issues.
+- getTask now correctly takes TaskQueryParams as an argument vs TaskIdParams in accordance with the A2A spec.
+- AgentBuilder now returns a unique messageId for each status update instead of the original user provided messageId.
+- In a future release the following packages will be set as peer dependancies to reduce the size of the build:  `@modelcontextprotocol/sdk`, `@trpc/server`, `cors`, `express`
+
 ## Features
 
 - **Modular Design:** Everything you need to get started building collaborative agents + its flexible enough for advanced configuration.
@@ -53,10 +61,10 @@ npm install @artinet/sdk
 ## Requirements
 
 - Node.js (v22.0.0 or higher recommended)
-
+<!-- 
 ## Documentation
 
-For more detailed documentation visit our documentation site [here](https://the-artinet-project.github.io/artinet-documentation/).
+For more detailed documentation visit our documentation site [here](https://the-artinet-project.github.io/artinet-documentation/). -->
 
 ## Example
 

examples/README.md

@@ -69,23 +69,6 @@ And after restarting the server, test persistence with:
 node examples/file-storage-client-continued.js
 ```
 
-### Code Deployment Examples
-
-These examples demonstrate how to prepare your agent code for deployment, including bundling and using the task handling proxies.
-
--   `examples/code-deployment.js`: Shows a JavaScript agent structured for deployment.
--   `examples/code-deployment.ts`: Shows a TypeScript agent structured for deployment, which will be bundled by the deployment process.
-
-These examples utilize `taskHandlerProxy` and `fetchResponseProxy` (from `examples/task-wrapper.js`, which is a simplified version of `src/utils/deployment/task-wrapper.ts`) to interact with a simulated deployment environment.
-
-## Test Deployment Feature
-
-The Artinet SDK now includes a **Test Deployment** feature. This allows you to bundle your agent code (as demonstrated in the Code Deployment Examples) and test its execution against a sandboxed deployment environment provided by Artinet. This is a crucial step for verifying your agent\'s behavior before a full deployment.
-
-You can see this in action in our internal tests (`tests/deployment.test.ts`), which use the `bundle` utility and the `testDeployment` function.
-
-**Coming Soon: Full Agent Deployment!** Beta users will get access to full serverless agent deployment capabilities in the coming days. This will allow you to host your agents directly on the Artinet platform, making them accessible to other agents and users. Stay tuned for more details!
-
 ## Known Issues
 
 - The file storage server does not properly maintain conversation history between restarts - it treats each message as if it were the first message in a conversation