feat(worklog): name the reference a skill read delivered, and double the row cap #1067
No reviewers
Labels
No labels
move-to-repo
coilyco-bridge-deploy
move-to-repo
coilyco-flight-deck-agent-compose
move-to-repo
coilyco-gaming-eco-app
move-to-repo
coilysiren-inbox
move-to-repo
unknown
🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-gaming/sirens-echo!1067
Loading…
Reference in a new issue
No description provided.
Delete branch "skill-read-worklog-detail"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Kai asked for the
> ✅ 📖 astronomyform on the tool progress surfaces and a doubled report cap.What changed
skills.read_skillrow names the reference it delivered:> ✅ 📖 astronomyon the worklog element,> 🔨 ✅ 📖 astronomyin the disclosure footer. In-flight rows stay plain and resolve into the named form.Detailfield onToolResultandExecutedTool, set only on the skill session's validated-path success branch, so the "arguments are never shown" rule keeps its teeth structurally: a refused or failed read can never echo the model's guessed path, pinned by test.×2.maxWorklogRowsdoubles from 6 to 12 (SIRENS_ECHO_WORKLOG_ROWSstill overrides). The disclosure footer has no row cap to double: it already lists every call and yields only to Discord's own message ceiling.docs/sirens-echo-worklog.mdcarries the carve-out and the new example;docs/sirens-echo-tool-markup.mdpoints at it (that doc is 7993 of its 8000-char cap).Verification
Six new tests in
skillreaddetail_test.gocover the validated-detail path, the refusal-names-nothing guarantee, both rendered forms, the notice-shape conformance, and the no-collapse-across-references rule.just testand the full pre-commit suite are green.🤖 Generated with Claude Code