Agent-Field/CodeAF

Seen on dev@debffabf6. Surfaced while verifying #1424; not introduced by it. What happened The sample tab rows in screen.md and home.md show spacing after home that differs from the actual row after #1424's alignment change. They are presented as visual examples, so the cell positions are part of the instruction. Replication Deterministic (no model). Run codeaf manual "how are conversation tabs laid out", then capture the first row of codeaf chat on a standard-width terminal and compare the spaces following home. The two manual samples differ from the captured row. Where internal/manual/chat/screen.md:103 and internal/manual/chat/home.md:592 at dev@debffabf6 contain the schematic rows; the current rendering is in internal/tui3/hometabs.go. The fix Make the examples accurately show the current row's spacing, or label them explicitly as schematic without implying exact cells. Acceptance e2e: both codeaf manual answers show a tab sample whose home spacing matches a captured codeaf chat r

Seen on dev@debffabf6. Surfaced while verifying #1415; not introduced by it. What happened The Home screenshot's alt text says scheduled and names the older panel arrangement. The current Home panel is standing; the text gives screen-reader users a description of a different page. Replication Deterministic (no model). Read the Home image alt text in README.md, then run make demo-home and inspect Home's panel headings. The alt text includes scheduled; the live heading is standing. Where README.md:85 at dev@debffabf6 contains Home in two columns: needs you, unread, where you were, running and scheduled on the left; projects, spend and since you left on the right. The fix Describe the screenshot and current Home layout in the image's alt text using the visible panel names. Acceptance e2e: the rendered README's Home image has alt text matching the headings in codeaf chat on a demo home. Unit: a documentation check catches retired Home panel names in current image descriptions. Record the

Seen on dev@debffabf6. Surfaced while verifying #1415; not introduced by it. What happened The manual says a waiting order appears on Home with when it goes off at the right — in 20h, mon 8:30. The standing panel deliberately leaves the right side blank. A reader expecting the due time there sees none. Replication Deterministic (no model). Run make demo-home, open Home, and compare a waiting row of standing with codeaf manual "when does a standing order go off on home". The page promises a right-side time; the rendered row does not draw one. Where internal/manual/chat/home.md:1681 at dev@debffabf6 contains the promise. The standing panel's row rendering is in internal/tui3/homepanel_standing.go and homecell.go. The fix Remove the right-side-time promise from this Home section and point to the standing place for the due reading, unless the intended design is changed to show that time on Home. Acceptance e2e: codeaf manual "when does a standing order go off on home" describes the same

Found on santos/dev2 at 008363c98 (#1410). It reaches dev when #1410 merges. What happened The manual locates task.parallel in category spending. /settings shows it under Tasks as tasks at once, so someone following the page searches the wrong section. Replication Deterministic (no model). Run codeaf manual "where is task.parallel", then open /settings in codeaf chat. The answer says spending; the visible row is under Tasks and reads tasks at once. Where internal/manual/chat/tasks.md:4219 gives the wrong category at 008363c98. internal/config/settings.go:2347 defines the visible label and category. The fix Replace the category with Tasks and name the row exactly as drawn. Acceptance e2e: the manual command says Tasks and tasks at once, matching /settings. Unit: a manual probe for the setting reaches the corrected section. The change entry's invalidates notes the former category.

Found on santos/dev2 at 008363c98 (#1410). On dev@debffabf6 too. What happened The documented command names docs/benchmarks/measure-cli.sh, which does not exist. The executable is docs/benchmarks/performance/measure-cli.sh. The same stale path is on dev. Replication Deterministic (no model). From a clean checkout, run the README's path with --help. The shell reports that the file does not exist. Run docs/benchmarks/performance/measure-cli.sh --help; it prints usage. Where docs/benchmarks/performance/README.md:10 contains the stale command. The script's own example at docs/benchmarks/performance/measure-cli.sh:7 also uses the stale path, at 008363c98. The fix Use the existing performance/measure-cli.sh path in both examples. Acceptance e2e: both documented --help commands execute from the repository root and print the script's usage. Unit: a documentation check resolves every local script path in these examples. The change entry's invalidates names the former path.