No description
Find a file
Madhura68 c39b337fcc feat(ST-707): log tools — implementation, test_result, commit
Three write tools that append StoryLog entries:
- log_implementation: type=IMPLEMENTATION_PLAN
- log_test_result: type=TEST_RESULT, status PASSED|FAILED
- log_commit: type=COMMIT with hash and message

All accept optional metadata in input but skip writing it for now —
the StoryLog.metadata JSONB column lands with Scrum4Me PR #2.
After that PR merges, run sync-schema and add `metadata` to each
prisma.create's data field.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-26 23:06:50 +02:00
prisma feat(ST-702): vendor Scrum4Me schema via submodule + sync script 2026-04-26 23:00:29 +02:00
scripts feat(ST-702): vendor Scrum4Me schema via submodule + sync script 2026-04-26 23:00:29 +02:00
src feat(ST-707): log tools — implementation, test_result, commit 2026-04-26 23:06:50 +02:00
vendor feat(ST-702): vendor Scrum4Me schema via submodule + sync script 2026-04-26 23:00:29 +02:00
.env.example feat(ST-701): scrum4me-mcp repo skeleton 2026-04-26 22:57:27 +02:00
.gitignore feat(ST-701): scrum4me-mcp repo skeleton 2026-04-26 22:57:27 +02:00
.gitmodules feat(ST-702): vendor Scrum4Me schema via submodule + sync script 2026-04-26 23:00:29 +02:00
package-lock.json feat(ST-701): scrum4me-mcp repo skeleton 2026-04-26 22:57:27 +02:00
package.json feat(ST-702): vendor Scrum4Me schema via submodule + sync script 2026-04-26 23:00:29 +02:00
tsconfig.json feat(ST-701): scrum4me-mcp repo skeleton 2026-04-26 22:57:27 +02:00