Skip to content

History / Requirement Specification Tree Modernized

Revisions

  • docs(wiki): close the #1696 known limitation on the #1695 tree page (Refs #1696)

    @github-actions github-actions[bot] committed Oct 5, 2026
  • reqSpecListTree: post-review corrections for #1699 (dead deep link, container=0, banner wording)

    opencode-agent committed Sep 28, 2026
  • Requirement Spec Tree (#1699): container children re-parented into a specification Closes the read-parity gap #1699 in the modernized navigator. The 1.9.20 lazy loader walked any child node type of a specification, so a test project node re-parented under one (req_cfg->child_requirements_mgmt, the default) and the requirements hanging off it appeared in the old tree. The modern navigator dropped the branch silently. - init returns containers[] per specification (node_type_id = 1 children, live count, openable flag); children accepts &container=, proven to be a child of the addressed specification of the addressed project. - The tree renders the container as an expandable row merged into the specification's children by node_order, id - the sequence legacy emitted. - 3 new i18n keys in all 10 bundles. - Also documents the undefined-array-key defect fixed on the same code path.

    opencode-agent committed Sep 28, 2026
  • Requirement Specification Tree (reqSpecListTree): honest suite result 50/51 + 1 known FAIL (#1696) - Refs #1695

    opencode agent committed Sep 28, 2026
  • Requirement Specification Tree navigator (reqSpecListTree) modernized - Refs #1695

    opencode agent committed Sep 28, 2026