Refactor Mattermost and Slack integration workflows to remove legacy Fidelity variables, streamline command execution, and enhance documentation for project profiles. Update scripts and README files to reflect changes in directory structure and configuration precedence, ensuring a consistent approach to project knowledge management across profiles. Improve error handling and validation in profile creation and doctor commands, and enhance test coverage for profile-related functionalities.
This commit is contained in:
@@ -77,13 +77,23 @@ Source filters for profile-bounded reads. For example, a Mattermost profile can
|
||||
|
||||
## Adding A New Project
|
||||
|
||||
1. Copy `profiles/example/` to `profiles/<new-project>/`.
|
||||
2. Create or point to a project knowledge vault.
|
||||
3. Define services only for integrations the project actually uses.
|
||||
4. Put connector secrets in ignored `.env` files.
|
||||
1. Create the isolated profile and workspace:
|
||||
|
||||
```bash
|
||||
python3 scripts/aiw/profile.py create my-project --display-name "My Project"
|
||||
```
|
||||
|
||||
2. Define services only for integrations the project actually uses.
|
||||
3. Put connector secrets in ignored `.env` files.
|
||||
4. Validate the layout:
|
||||
|
||||
```bash
|
||||
python3 scripts/aiw/profile.py doctor --profile my-project
|
||||
```
|
||||
|
||||
5. Build the local index.
|
||||
6. Connect AI clients through the MCP server.
|
||||
|
||||
## Migration Rule
|
||||
|
||||
Reusable code should accept a `--profile` argument and resolve paths through profile configuration. Avoid adding new hardcoded references to Fidelity, channel names, ticket prefixes, or company-specific folders in generic scripts.
|
||||
Reusable code should accept a `--profile` argument and resolve paths through profile configuration. Avoid adding hardcoded references to Fidelity, channel names, ticket prefixes, or company-specific folders in generic scripts.
|
||||
|
||||
Reference in New Issue
Block a user