[bassilkhilo-ag2]

What

19 structural tests covering two merged PRs with no existing test coverage.

Source files tested:

• src/discord-bridge.py — task-file channel/guild metadata fields
• src/inline-tools.ts — workspace skills scan path

---

PR #1077 — channel_name + guild_name in task files (12 tests)

Background: Task files previously only carried numeric channel_id. After a real misroute incident (core agent had to guess channel identity by grepping numeric IDs against a memory file), two additive human-readable fields were added alongside channel_id.

Test	Verified
channel_name field present in task_file.write_text()	✓
guild_name field present in task_file.write_text()	✓
channel_name appears AFTER channel_id (additive, no breaking change)	✓
DM fallback: getattr(message.channel, "name", None) or "DM"	✓
Guild fallback: message.guild.name if message.guild else "DM"	✓
Newline sanitization .replace("\n", " ") (injection guard)	✓
Both fields in same write block	✓
Comment documenting human-readable purpose	✓

---

PR #1081 — inline-tool loader scans $SUTANDO_WORKSPACE/skills/ (7 tests)

Background: Before this PR, users couldn't park personal inline-tool skills in their workspace without forking the repo. $SUTANDO_WORKSPACE/skills/ was added as the second scan path in both loadSkillManifestTools() and loadCoreDocumentedSkills(), with scan order: repo → workspace → memory-dir (last-write-wins).

Test	Verified
loadSkillManifestTools() includes WORKSPACE_DIR/skills	✓
loadCoreDocumentedSkills() includes WORKSPACE_DIR/skills	✓
Both REPO_ROOT/skills and WORKSPACE_DIR/skills present	✓
Scan order: REPO_ROOT < WORKSPACE_DIR (repo → workspace → memory)	✓
last-write-wins convention documented	✓

🤖 Generated with Claude Code

[VasiliyRad]

Tests look solid — assertions are correct, escape handling is right (double-backslash for literal \n match), and the invariants are meaningful.

One blocker: build_log.md is in .gitignore (line 33) and should not be committed. It contains workspace-specific operational state (proactive loop passes, content drafts, push go-ahead lists). Please remove it from this PR.

Non-test change: src/health-check.py modification (adding _pid_script helper for multi-PID source-path enrichment) is clean and correct — ps -o command= extraction with .py suffix filtering and graceful ? fallback.

The 24 structural tests across both files correctly verify the #1077 and #1081 invariants. False-positive risk is inherent to grep-style tests but acceptable and documented. LGTM once build_log.md is dropped.

[VasiliyRad]

Tests pass (19/19 discord-bridge-task-channel-metadata, 5/5 health-check-bridge-multi-pid). Quality looks good — structural source-grep pattern is appropriate here.

Two bundling issues to flag:

1. src/health-check.py is a production fix, not a test. Commit d9a384c (the multi-pid path enrichment) is the implementation; health-check-bridge-multi-pid.test.py tests it. Both are welcome, but the PR title says 'structural tests for #1077 and #1081' — this is a third change (#1084-equivalent) that isn't mentioned in the title or PR body table. Please add a '## health-check multi-pid path enrichment' section to the PR body so reviewers know they're also reviewing a source change, not just tests.

2. build_log.md doesn't belong in test PRs. The proactive loop's pass log is runtime state, not source. It can be committed to main directly or via a chore PR, but it dilutes the diff here and makes future bisects harder. Please strip it from this branch before merge.

The src/health-check.py change itself is correct and safe — the inner _pid_script helper is well-guarded with try/except and a 3s timeout.

[bassilkhilo-ag2]

Branch rebased onto origin/main — bundled junk (build_log.md, health-check.py, health-check-bridge-multi-pid.test.py) stripped. Diff is now clean: only the intended test file(s).