// Shared filing policy for Issue tools and Driver attention guidance.
var FILING_GUIDANCE =
  "Automatic Issue filing is for established project problems and durable project backlog. The baseline is the repository default branch or the established release/integration target; never assume its name is main or that the current checkout is the baseline. " +
  "Before automatically filing a bug found in a branch, worktree, or dirty checkout, establish with read-only evidence that it also affects that baseline independently of the current edits. Record the baseline ref/commit and supporting reproduction or code evidence in the Issue. Do not switch branches, reset changes, or modify the working tree merely to establish this. " +
  "Errors introduced by current edits, incomplete implementations, intermediate test/build failures, and work deferred only within the active task belong in that task and its concise Project Log, not a new Issue. Being unresolved, interrupted, or discovered in a worktree is not by itself a reason to file. If baseline impact is unknown, continue investigating or record the uncertainty and next action in the task Log; do not automatically file an Issue. " +
  "For an authorized Project Driver, once a defect is established on the baseline or independent durable project work is identified, proactively search or reuse an existing Issue, or create one without waiting for a separate user request. Record observable evidence, affected component, impact, next action, and acceptance criteria, then revise that same Issue with remediation and verification. " +
  "An explicit user request to track actionable work is also sufficient, including branch-specific work; label that scope clearly and do not claim baseline impact without evidence. Continue using an existing Issue for its active implementation instead of filing separate Issues for intermediate failures. ";

var NOTE_GUIDANCE =
  "For a confirmed, open Issue that still needs action, an authorized Project Driver should check active notes and create or reuse one short linked Sticky Note. This is an explicit exception to the default no-note and already-recorded rules. Keep the note to two lines: a short plain-text title and the exact opaque issue: reference returned by the Issue tools. Keep evidence, implementation details, and progress in the Issue, never in the note. Do not create duplicate notes or notes for unconfirmed task-local failures. Close the linked note when its Issue is resolved or closed; do not replace it with a completion summary. ";

module.exports = { FILING_GUIDANCE: FILING_GUIDANCE, NOTE_GUIDANCE: NOTE_GUIDANCE };