Skip to content

Block model-policy migration completion when preserved guidance still authorizes autonomous xhigh #174

Description

@BaseInfinity

Problem

The updater correctly preserves customized policy surfaces, but it can still record the current model-policy schema as fully migrated while those preserved files contain autonomous xhigh guidance.

The #86 final review proved the false-attestation path:

  • an AGENTS.md without trustworthy generated-file provenance is preserved byte-for-byte;
  • customized START-SDLC.md / SDLC-LOOP.md / repo skill files can also be preserved;
  • those files may still say Baseline reasoning: xhigh or Use xhigh reasoning by default for this repo.;
  • update nevertheless sets manifest.model_profile.policy_schema_version to the latest schema, removes the legacy field, and converges without revisiting the unresolved policy conflict.

Preserving user customization is required. Claiming migration completion while effective repo guidance still authorizes autonomous xhigh is not.

Acceptance criteria

  • Detect unresolved autonomous-effort guidance in every customized or untracked policy surface skipped during model-policy migration.
  • Preserve customized files byte-for-byte unless the user explicitly selects replacement.
  • Do not record the latest model-policy schema as complete while any skipped policy surface still conflicts with the High-only contract.
  • Emit an explicit, actionable, repeatable unresolved-conflict result naming each path; a second update must not silently report convergence.
  • Continue applying unrelated safe repairs without falsely certifying the policy migration, or fail before mutation if atomicity requires it; choose and document one deterministic contract.
  • Distinguish structured selected-profile configuration from arbitrary persisted prose and keep explicit mixed-profile preservation intact.
  • Add RED/GREEN regressions for missing generated provenance, customized generated docs, fully customized policy surfaces, and clean non-conflicting customization.
  • Prove PowerShell parity: document/test that install.ps1 schema_version = 2 belongs to the model-profile file rather than manifest model-policy schema, and that PowerShell emits no legacy escalation_reasoning authority.
  • Keep the fix(review): stop tool-free cross-model reviews when Claude invokes advisor #158 one-time exception consumed; require normal Sol High + Fable High review with no exception.
  • Synchronize ROADMAP and the authoritative 1.0 milestone in this slice.

Evidence source

#86 final candidate 7cfa28ec0add78c706cd24f28b15a9e9e99d023b passed canonical 11/11, then the required reviewers converged after one reconciliation on a P1: schema migration completion is false when preserved policy still authorizes autonomous xhigh. The receipt is non-certifying and no retry is recommended.

Non-goals

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingpriority: P0Stop-the-line critical path; work before lower-priority roadmap items

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions