wip: autosync .gitignore,technical-research/accounting-inventory.json,technical-research/accounting.json#2
wip: autosync .gitignore,technical-research/accounting-inventory.json,technical-research/accounting.json#2wranngle wants to merge 3 commits into
Conversation
Migrated 2026-05-06 from the legacy ~/.claude/docs/ shelf with prepended provenance header. Cross-references the existing voice-agent-elevenlabs-patterns.md and n8n project's AGENTS.md governance rules. Lives in workflow-patterns/ (alongside other prescriptive how-to docs) rather than technical-research/ (which holds system-schema JSON). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8c60db8d70
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -1,65 +0,0 @@ | |||
| { | |||
There was a problem hiding this comment.
Deleting technical-research/crm.json leaves the repository's documented quick-start command (cat technical-research/crm.json in README.md) pointing at a file that no longer exists. In a fresh checkout this makes the primary usage example fail immediately; either keep a durable CRM schema or update the README to reference one of the remaining files such as hubspot.json or salesforce.json.
Useful? React with 👍 / 👎.
|
|
||
| ## Components | ||
|
|
||
| 1. **Error Handler Workflow**: A dedicated workflow (`templates/n8n/error-handler-framework.json`) that processes errors and sends notifications. |
There was a problem hiding this comment.
This new pattern tells users to import templates/n8n/error-handler-framework.json, but I checked the repository with rg --files and there is no templates/ entry or error-handler-framework file. Anyone following the installation steps from a fresh checkout will be blocked at the import step unless the template is committed or the instructions point to an existing artifact.
Useful? React with 👍 / 👎.
wranngle
force-pushed
the
wip/autosync/local/main
branch
from
8c60db8 to
0b19376
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0b19376bf4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ## Best Practices | ||
|
|
||
| - **Centralization**: Use ONE error handler workflow for all your production workflows. This makes it easy to update notification logic (e.g., switching from Slack to PagerDuty) in one place. | ||
| - **Environment Context**: The framework uses `process.env.N8N_BASE_URL` to generate execution links. Ensure this environment variable is set in your n8n instance. |
There was a problem hiding this comment.
For self-hosted n8n users following this monitoring pattern, the generated execution links will stay blank or point at the wrong host because N8N_BASE_URL isn't one of n8n's documented URL settings, and Code/expression access is through n8n metadata such as $env; the public editor/webhook URLs are configured with variables like N8N_EDITOR_BASE_URL or WEBHOOK_URL. Please update the pattern to use the actual n8n URL variable your handler reads so alerts contain usable execution links.
Useful? React with 👍 / 👎.
wranngle
force-pushed
the
wip/autosync/local/main
branch
2 times, most recently
from
01339c0 to
6904db0
Compare
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
wranngle
force-pushed
the
wip/autosync/local/main
branch
from
6904db0 to
63eea0e
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 63eea0ed39
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "generated": true | ||
| } | ||
| }, | ||
| "integration_lookup": { |
There was a problem hiding this comment.
This deletion removes the only checked-in manifest for integration discovery: the file describes itself as the index for integration estimation and contains integration_lookup entries (for example, elevenlabs maps to the surviving voice-ai-agency-data-storage-infrastructure.md). I checked the current tree with rg --files and there is no replacement index, while the new cleanup rule only says to drop runtime DBs, proactive reports, and JSON marked generated: true; this file is neither generated nor runtime state, so consumers can no longer discover the remaining curated research by integration name.
Useful? React with 👍 / 👎.
wranngle
force-pushed
the
wip/autosync/local/main
branch
from
63eea0e to
96e378c
Compare
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
wranngle
force-pushed
the
wip/autosync/local/main
branch
from
96e378c to
44c6e75
Compare
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
wranngle
force-pushed
the
wip/autosync/local/main
branch
from
44c6e75 to
4ed62b1
Compare
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
wranngle
force-pushed
the
wip/autosync/local/main
branch
from
4ed62b1 to
e47fa47
Compare
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
wranngle
force-pushed
the
wip/autosync/local/main
branch
from
e47fa47 to
5fca658
Compare
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
wranngle
force-pushed
the
wip/autosync/local/main
branch
from
5fca658 to
7b717b8
Compare
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
wranngle
force-pushed
the
wip/autosync/local/main
branch
3 times, most recently
from
9fca399 to
0f65523
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0f65523e34
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -1,70 +0,0 @@ | |||
| { | |||
| "integration": "EHR", | |||
There was a problem hiding this comment.
Deleting the EHR blueprint leaves the repository advertising electronic health record JSON schemas in the root README, but no matching EHR/healthcare schema remains in technical-research (checked with rg -i "ehr|health|fhir|athena|epic|cerner" technical-research workflow-patterns README.md, which now only finds the README claim and unrelated prose). Users looking for the documented EHR data shape can no longer load one; either keep a curated EHR schema or update the README to stop promising it.
Useful? React with 👍 / 👎.
wranngle
force-pushed
the
wip/autosync/local/main
branch
4 times, most recently
from
30b32c9 to
40bcaee
Compare
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
25 similar comments
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
…,technical-research/accounting.json Wip-Owner: autosync/local Wip-Base: main Wip-Run: 86cc0892-10d3-4c40-b3de-b3c090ec4403
|
Retired autosync namespace per git-awesome doctrine 2026-05-12. The |
1 participant
Wip-Owner: autosync/local
Wip-Base: main
Wip-Run: 99c03ded-b254-426d-80dd-b89f759ea580