Skip to content

Remove default placeholder text from room task descriptions #2930

Description

@mblua

Problem and requested behavior

Clean writes Ready to start a new topic into TASK.md, and empty-title room creation inserts the same persisted prose. Later task-append-body retains it above the human summary. Start with an empty task description after Clean and in new rooms; preserve Clean title/topic/status behavior and existing user-authored descriptions outside explicit Clean. UI must recognize the empty canonical state including repeated Clean. Update relevant tests and documentation. Editing/replacing descriptions through CLI belongs to #2931 and is excluded.

Approved technical plan (human gate pending)

Canonical immutable version3: D:/0_repos/AgentsCommander_iac/.ac/plans/2930-empty-task-description/plan-v3-empty-task-description.md and epic-v3.md.
Plan-SHA256: 1BBA355419DDC07D47D4F9B000EF507AAFC46D8B5D38EB1CD990DDAF95D9B808.
Architect, Rust, Grinch, UI and writer approved the same exact set. Mapping: phase-issues.json; consensus: round3-consensus-record.md in the same directory. Human Step7.5 approval and purge remain required before development.

Phase Child Class / owner Files Depends on
P01 #2935 patterned / UI 3 none
P02 #2936 patterned / Rust 3 P01 merged
P03 #2937 mechanical / writer 3 P02 merged

One sequential branch/PR per phase, each closing only its child. Close this epic after all three land and exact-head checks pass. No final build or artifact requested. User authorized removing redundant final build and local Rust guards in UI/docs; relevant checks and CI remain.

Acceptance

  • Clean leaves body empty, with title/topic/status, BOM/EOL and failure recovery retained; repeated canonical Clean is NoOp without extra backups/topic.
  • New room defaults persist only 23-byte LF Clean frontmatter, no placeholder body; explicit USER titles retained.
  • Existing human/legacy descriptions are unchanged outside explicit Clean; first append after Clean contains only human summary.
  • Both menus recognize exact empty body and preserve legacy/status/unknown guards; whitespace remains cleanable.
  • Documentation consistently states empty body and Clean23/23, preserving USER37 and native gates; no claims of native tests executed.

Activity

  1. mblua commented on Oct 7, 2026

    @mblua
    OwnerAuthor

    Technical scoring on main 0e2c719, based on verified investigation.

    Category Score Anchor / evidence
    Scope footprint 8 Three production points plus related tests/docs in eight files; below coherent-module anchor 10.
    Diagnosis difficulty 1 Issue states exact cause; source confirms literal writes and comparison.
    Domain knowledge 4 Ordinary Rust/TS with existing paired TASK/status transaction rules.
    Solution-space ambiguity 4 Empty default is specified; whitespace and legacy UI recognition need exact decision.
    Blast radius and reversibility 5 Local Clean/new-room paths, standard revert; no migration requested.
    Dependency and integration load 4 Rust snapshot and UI consumer must agree; no external dependency.
    Verification difficulty 6 Existing unit/UI harnesses cover cases; adjust expectations and prove idempotence/preservation.
    State, data and compatibility 6 Persisted default body changes, existing format and transaction retained; no schema/migration.
    Concurrency and timing 3 Existing paired transaction/watchers unchanged, protect current regression tests.
    Environment and tooling 2 Existing Windows Rust/npm harness, no environment change.

    Raw sum: 43. Final: round((43-10)/190*99)+1 = 18/100.

    Excluded ceremony: issue/branch/PR, push, CI wait, plan/review/delegation, merge and cleanup.

    Selected path: Full due to cross-surface Rust persistence defaults and UI clean-state behavior. Architect owns plan; Rust and Grinch approve exact version/digest. Architect determines minimal coherent ownership/partition using actual file inventory; no implementation before agreed plan and human approval. No build requested. I2931 excluded.

  2. added
    EpicLarge cross-cutting work item
    on Oct 7, 2026
  3. mblua commented on Oct 7, 2026

    @mblua
    OwnerAuthor

    I2930 aprobación humana v3 — recibo inmutable

    Usuario respondió «aprobado» a la presentación del conjunto v3, tablas de impacto, fases y mapping. Autoriza ejecución y entrega de P01→P02→P03 conforme especificación aprobada; no build final extra ni artefacto solicitado. No instalación/release.

    Epic2930; plan D:/0_repos/AgentsCommander_iac/.ac/plans/2930-empty-task-description/plan-v3-empty-task-description.md y epic-v3.md, bytes idénticos. Plan-SHA256 1BBA355419DDC07D47D4F9B000EF507AAFC46D8B5D38EB1CD990DDAF95D9B808. Cinco acuerdos verificados round3-consensus-record.md, mismo set exacto.

    Identidad aprobada, base rutas D:/0_repos/AgentsCommander_iac/.ac/plans/2930-empty-task-description/:

    • P01: child2935; branch fix/2935-empty-clean-ui; P01-v3-ui-empty-description.md; SHA256 769B234951DAA1864DAA5829BD10A1BAD0A7E4410995E7F62534093329BC376C; sin dependencias.
    • P02: child2936; branch fix/2936-empty-task-defaults; P02-v3-rust-empty-defaults.md; SHA256 717F99B2264ADB28CC3FB571752D77B31F761497E1EB83B001762F9940E074DC; dependsP01.
    • P03: child2937; branch docs/2937-empty-task-description; P03-v3-docs-empty-defaults.md; SHA256 BF230DF00AAE54F3CC33B635690D7DA04C6EBA30ED4F2BF45A640ED4663A098C; dependsP02.

    Mapping phase-issues.json verificado: cada fase una vez, hijos únicos abiertos y vinculados nativamente a2930; ramas únicas. SHA set recalculado tras mapping y aprobación, coincide. Equipo completo no vacío, reports recibidos y todos working:false. Step7.5 dry-run/real-purge/rehash por registrar en ejecución externa; no modificar este recibo ni planes. Rama preliminar fix/2930-empty-task-description sin commits propios/producto se retira de trabajo activo antes de P01, conforme partición.

  4. mblua commented on Oct 7, 2026

    @mblua
    OwnerAuthor

    All three children delivered; receipts and exact-head CI evidence are recorded in the final delivery comment.

  5. mblua commented on Oct 7, 2026

    @mblua
    OwnerAuthor

    Delivered all three phases of the approved empty-task-description plan:

    P03 independent review passed and all applicable exact-head CI checks passed for da5f523. Full-tier jobs were officially skipped (run 3213, full=false). Local main is clean and equals origin/main at 938dfc2. No additional package, installation, release, or native test execution was requested. I2931 and E2787 remain separate work.

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

    EpicLarge cross-cutting work itemenhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions