@clawbot please apply appropriate labels to this task. read the readmes for upaas pixa mfer netwatch and autistmask to get an example of the level of completeness i'm looking for. also review all code style standards in sneak/prompts (prompts subdir) as well as the go http server guidelines and create issues in this repo for all divergences.
@clawbot please apply appropriate labels to this task. read the readmes for upaas pixa mfer netwatch and autistmask to get an example of the level of completeness i'm looking for. also review all code style standards in sneak/prompts (prompts subdir) as well as the go http server guidelines and create issues in this repo for all divergences.
clawbot
self-assigned this 2026-03-01 16:59:03 +01:00
I have a compliance worker already running for issue #1 + issue #2 that is making initial README improvements. Once that PR lands, I will:
Read READMEs from upaas, pixa, mfer, netwatch, and AutistMask to understand the completeness bar
Review all code style standards in sneak/prompts (CODE_STYLEGUIDE.md, CODE_STYLEGUIDE_GO.md, GO_HTTP_SERVER_CONVENTIONS.md, etc.)
Audit webhooker code against those standards
Create individual issues for each divergence
Dispatch a worker for the comprehensive README rewrite
Waiting for the current compliance PR to avoid merge conflicts on the same files.
Labels applied. Assigned to clawbot.
I have a compliance worker already running for [issue #1](https://git.eeqj.de/sneak/webhooker/issues/1) + [issue #2](https://git.eeqj.de/sneak/webhooker/issues/2) that is making initial README improvements. Once that PR lands, I will:
1. Read READMEs from upaas, pixa, mfer, netwatch, and AutistMask to understand the completeness bar
2. Review all code style standards in `sneak/prompts` (CODE_STYLEGUIDE.md, CODE_STYLEGUIDE_GO.md, GO_HTTP_SERVER_CONVENTIONS.md, etc.)
3. Audit webhooker code against those standards
4. Create individual issues for each divergence
5. Dispatch a worker for the comprehensive README rewrite
Waiting for the current compliance PR to avoid merge conflicts on the same files.
in the new README i would like a very clear description of the data model. i have included some of the entities/tables in the current README but you can probably get a much better mental model of it together and document it much more clearly. i'd like you to come up with a new name for the main entity in the application which i am calling the 'processor' now which is basically "a webhook" - maybe those are called 'webhooks' and the URLs under /webhooks/<uuid> can be called 'entrypoints` or something.
i left a note on the compliance PR about the sqlite setup i'd like to use (one sqlite file for the main app and all normal webapp stuff, then one sqlite file per "webhook"/"processor" which stores the input logs, the output queues, and the internal processing logs).
in the new README i would like a very clear description of the data model. i have included some of the entities/tables in the current README but you can probably get a much better mental model of it together and document it much more clearly. i'd like you to come up with a new name for the main entity in the application which i am calling the 'processor' now which is basically "a webhook" - maybe those are called 'webhooks' and the URLs under `/webhooks/<uuid>` can be called 'entrypoints` or something.
i left a note on the compliance PR about the sqlite setup i'd like to use (one sqlite file for the main app and all normal webapp stuff, then one sqlite file per "webhook"/"processor" which stores the input logs, the output queues, and the internal processing logs).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
@clawbot please apply appropriate labels to this task. read the readmes for upaas pixa mfer netwatch and autistmask to get an example of the level of completeness i'm looking for. also review all code style standards in sneak/prompts (prompts subdir) as well as the go http server guidelines and create issues in this repo for all divergences.
Labels applied. Assigned to clawbot.
I have a compliance worker already running for issue #1 + issue #2 that is making initial README improvements. Once that PR lands, I will:
sneak/prompts(CODE_STYLEGUIDE.md, CODE_STYLEGUIDE_GO.md, GO_HTTP_SERVER_CONVENTIONS.md, etc.)Waiting for the current compliance PR to avoid merge conflicts on the same files.
in the new README i would like a very clear description of the data model. i have included some of the entities/tables in the current README but you can probably get a much better mental model of it together and document it much more clearly. i'd like you to come up with a new name for the main entity in the application which i am calling the 'processor' now which is basically "a webhook" - maybe those are called 'webhooks' and the URLs under
/webhooks/<uuid>can be called 'entrypoints` or something.i left a note on the compliance PR about the sqlite setup i'd like to use (one sqlite file for the main app and all normal webapp stuff, then one sqlite file per "webhook"/"processor" which stores the input logs, the output queues, and the internal processing logs).
ok you may proceed, compliance PR is merged