Skip to content

docs(roadmap): add #418 — system-prompt json sections[] exposes internal __SYSTEM_PROMPT_DYNAMIC_BOUNDARY__ sentinel#2962

Open
code-yeongyu wants to merge 1 commit intomainfrom
docs/roadmap-418-system-prompt-boundary-sentinel-leaked
Open

docs(roadmap): add #418 — system-prompt json sections[] exposes internal __SYSTEM_PROMPT_DYNAMIC_BOUNDARY__ sentinel#2962
code-yeongyu wants to merge 1 commit intomainfrom
docs/roadmap-418-system-prompt-boundary-sentinel-leaked

Conversation

@code-yeongyu
Copy link
Copy Markdown
Collaborator

Pinpoint #418

system-prompt --output-format json exposes "__SYSTEM_PROMPT_DYNAMIC_BOUNDARY__" as a literal element in sections[].

Evidence:

{"sections": [
  "You are an interactive agent...",
  "# System\n...",
  "# Doing tasks\n...",
  "# Executing actions with care\n...",
  "__SYSTEM_PROMPT_DYNAMIC_BOUNDARY__",  ← internal sentinel leaked
  "# Environment context\n...",
  "# Project context\n...",
  "# Claude instructions\n...",
  "# Runtime config\n..."
]}

Internal split delimiter at index 4, indistinguishable from real sections by type. Automation iterating sections[] must special-case it or misprocess it as a real section.

ROADMAP-only PR. No source/test changes.

@Yeachan-Heo
Copy link
Copy Markdown
Contributor

Review verdict: APPROVE

Inspected exact diff against origin/main: docs-only ROADMAP.md change (+2), no source/test/schema/runtime contract files touched. CI is green and merge state is CLEAN.

The #418 pinpoint is concrete and actionable: it names system-prompt --output-format json, the exact leaked sentinel __SYSTEM_PROMPT_DYNAMIC_BOUNDARY__, where it appears (sections[]), why automation misprocesses it as a real section, and the expected fix/regression direction.

Non-duplicative: nearby JSON/help contract items cover other command surfaces and schema issues; this specifically tracks the system-prompt section-boundary sentinel leak.

Merge risk: low. Blockers: none.


[repo owner's gaebal-gajae (clawdbot) 🦞]

itwizardo pushed a commit to itwizardo/hackcode that referenced this pull request Apr 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants