Hardik
080dafb473
Portal issues now file with only the 'portal' label. The watcher runs two phases:
1. Triage — Claude reads each untriaged 'portal' issue (analysis only), posts a
requirements-breakdown comment, and routes it to 'claude-queue' (auto-fixable)
or 'interactive' (needs human steering).
2. Fix — unchanged; processes 'claude-queue' issues into PRs.
The triage breakdown is posted without the bot marker so the fix stage reads it
back as refined requirements.
PS 5.1 fixes found while validating:
- Send API bodies as UTF-8 bytes (Invoke-RestMethod mangled non-ASCII, e.g. the
em-dash in Claude's breakdown, so Forgejo rejected the JSON)
- Build the labels array body by hand (ConvertTo-Json unwraps a single-element
array to a scalar, which Forgejo rejects)
- Triage output via two plain files (label + markdown) instead of one JSON blob
(embedded-newline markdown broke ConvertFrom-Json)
- Read triage files as UTF-8; additive label POST + a guard so Set-IssueLabels
can never wipe an issue's labels
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
13 lines
437 B
JSON
13 lines
437 B
JSON
{
|
|
"forgejoUrl": "https://git.pelagiamarine.com",
|
|
"repo": "shad0w/pelagia-portal",
|
|
"token": "<forgejo token with write:issue,write:repository>",
|
|
"workDir": "C:\\Users\\shad0w\\Documents\\src\\pelagia-autofix",
|
|
"baseBranch": "master",
|
|
"branchPrefix": "claude/issue-",
|
|
"maxIssuesPerRun": 1,
|
|
"maxTriagePerRun": 3,
|
|
"claudeExe": "C:\\Users\\shad0w\\.local\\bin\\claude.exe",
|
|
"claudeMaxTurns": 150,
|
|
"triageMaxTurns": 80
|
|
}
|