[P1-08] Fix ambient repository context wiring #31

Closed
opened 2026-08-28 20:54:39 +01:00 by conductor · 2 comments
Owner

Plain summary

Repository/files/functions context is computed in the right place (behind the ContextBroker) and only when a coding task actually warrants it — not scanned on every app init.

Example

No repo scan occurs unless the result is actually consumed; the prompt trace shows the selected repository context.

Technical details

Parent epic: #16

Manifest ID: P1-08

Priority: P1
Problem: repo/files/functions context can be computed on RuneApp but looked up on RuneTask.

Action:

  • move project-context discovery behind ContextBroker;
  • attach typed results to CognitiveJob/TaskState;
  • only compute when coding task warrants it.

Acceptance criteria:

  • no repo scan occurs unless result is actually consumed;
  • prompt trace shows selected repository context.

Dependencies: P0-03, P1-07.


Resolved dependency references

  • Depends on: #19 (P0-03), #30 (P1-07)
  • Blocks: None.

Relevant source files

Not specified in the handoff. P0-01 must identify authoritative paths before implementation; do not guess by adding another path.

Do not do

  • Do not begin this issue before its dependencies are complete.
  • Do not create a parallel authority path; replace, extend, or remain dormant.
  • Do not add unrelated cognitive subsystems or additive feature growth.
  • Do not treat module/schema existence, background activity, or model self-report as acceptance evidence.

Source directive

Preserved from /home/nick/Desktop/rune_v1_course_correction_handoff.md, Section 14. The handoff is authoritative if this issue summary is ambiguous.

Pipeline requirements

  • TDD: frozen/regression tests written first, red → green
  • ruff check and ruff format --check clean
  • Spec-compliance review gate: PASS
  • Code-quality review gate: Approved
  • Full orchestration suite regression green
  • Canary passes (where applicable)
  • Closed with a properly formatted closing comment + commit/PR references
## Plain summary Repository/files/functions context is computed in the right place (behind the ContextBroker) and only when a coding task actually warrants it — not scanned on every app init. ## Example No repo scan occurs unless the result is actually consumed; the prompt trace shows the selected repository context. ## Technical details Parent epic: #16 Manifest ID: **P1-08** **Priority:** P1 **Problem:** repo/files/functions context can be computed on `RuneApp` but looked up on `RuneTask`. **Action:** - move project-context discovery behind ContextBroker; - attach typed results to CognitiveJob/TaskState; - only compute when coding task warrants it. **Acceptance criteria:** - no repo scan occurs unless result is actually consumed; - prompt trace shows selected repository context. **Dependencies:** P0-03, P1-07. --- ## Resolved dependency references - Depends on: #19 (P0-03), #30 (P1-07) - Blocks: None. ## Relevant source files Not specified in the handoff. P0-01 must identify authoritative paths before implementation; do not guess by adding another path. ## Do not do - Do not begin this issue before its dependencies are complete. - Do not create a parallel authority path; replace, extend, or remain dormant. - Do not add unrelated cognitive subsystems or additive feature growth. - Do not treat module/schema existence, background activity, or model self-report as acceptance evidence. ## Source directive Preserved from `/home/nick/Desktop/rune_v1_course_correction_handoff.md`, Section 14. The handoff is authoritative if this issue summary is ambiguous. ## Pipeline requirements - [ ] TDD: frozen/regression tests written first, red → green - [ ] `ruff check` and `ruff format --check` clean - [ ] Spec-compliance review gate: PASS - [ ] Code-quality review gate: Approved - [ ] Full orchestration suite regression green - [ ] Canary passes (where applicable) - [ ] Closed with a properly formatted closing comment + commit/PR references
conductor added the P1 — highv1-course-correction labels 2026-08-28 20:54:39 +01:00
gitea-actions Bot added the buggrowth labels 2026-08-28 20:56:56 +01:00
gitea-actions Bot added the custodian label 2026-09-03 22:54:06 +01:00
conductor removed the bug label 2026-09-11 13:16:08 +01:00
Author
Owner

VERIFIED PROGRAMMATICALLY (no code change needed): the condition this issue targets already holds in-tree. See verification comment for the evidence.

VERIFIED PROGRAMMATICALLY (no code change needed): the condition this issue targets already holds in-tree. See verification comment for the evidence.
Author
Owner

CLOSED PROGRAMMATICALLY — commit 8bb31cd (contract BUILDER-2026-10-08T12:07:20Z-9c626b). The issue condition holds in-tree; the pinning tests prevent silent regression.

CLOSED PROGRAMMATICALLY — commit 8bb31cd (contract BUILDER-2026-10-08T12:07:20Z-9c626b). The issue condition holds in-tree; the pinning tests prevent silent regression.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: conductor/rune#31