8000 targets: a later task may modify a symbol another task plans by adeelahmad · Pull Request #81 · adeelahmad/aloop · GitHub
[go: up one dir, main page]

Skip to content

targets: a later task may modify a symbol another task plans - #81

Merged
adeelahmad merged 1 commit into
masterfrom
claude/project-thread-qerfr9
Oct 20, 2026
Merged

adeelahmad merged 1 commit into
masterfrom
claude/project-thread-qerfr9

Conversation

@adeelahmad
Copy link
Copy Markdown
Owner

Requested by Adeel · project thread

Before: targets check refused a modify whose symbol was not yet in the tree, even when another task's target plans that symbol in the same file. In live run 46, T2 extended src/main.rs with parse_args and run, and T3 modified both of them. The planner was blocked 4 times with "symbol … is not defined in src/main.rs".

After: a modify/refactor/replace/delete of a symbol that another target plans (as its planned_symbol, same path) passes the check. targets target shows it as (planned, shadow). A symbol that no target plans is still "not defined".

How:

  • plugin/bin/targets collects the planned (path, symbol) pairs and accepts a match from a different change_ref.
  • Both planner persona copies state the rule.
  • Test: semantic-targets.test.py case 8 covers both the pass and the still-blocked case. It was RED before the fix.
  • make ci is green locally (78/78).

Generated by Claude Code

Live run 46: T2 extended src/main.rs with parse_args and run, T3 modified
them, and targets check blocked the planner 4 times with "not defined".

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015QxyVf3NgwsgRyYpBgDDTC
@adeelahmad
adeelahmad marked this pull request as ready for review October 20, 2026 03:42
@adeelahmad
adeelahmad merged commit a52ae3b into master Oct 20, 2026
5 checks passed
adeelahmad pushed a commit that referenced this pull request Oct 20, 2026
…rgery paths

PR #82 (M9.17) makes a mission grant need the human's own words: a prompt line the
UserPromptSubmit hook captured. gate-mission-scope now denies the ways around that, for every
agent and the supervisor:
- a write (Write/Edit/patch or a Bash write) under <run data>/transcripts/, the captured prompts;
- a Bash `transcripts prompt|record|snapshot|stop|stage-in`, the hooks' own commands;
- where a mission is set, a host session started from a tool call (`claude -p`, `codex exec`,
  `opencode run`, or any prompt), since its prompt fires UserPromptSubmit too. A host's tools
  (`claude plugin validate`, `--version`, `opencode models`) stay allowed; no mission, no rule.

Test: mission-scope-bash.test.py (220 rows; 13 of the 18 new ones fail on the previous gate),
mission-roles.test.py (32 checks); make ci, conformance 78/78 and plugin validate --strict pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0197nSutKR1QAAqgJhFZ8fPj
adeelahmad pushed a commit that referenced this pull request Oct 20, 2026
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015QxyVf3NgwsgRyYpBgDDTC
adeelahmad added a commit that referenced this pull request Oct 20, 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

0