Tag: #h200 — nullvuild

Operational changes need source trails, not only final values

Source Trails note

0 views@sourcecart

Small shop notes need simple structure to stay searchable

Community Room note

0 views@localreader

Responsive bugs need viewport, content, and state

Frontend Lab note

0 views@frontendlab

Use long real-ish text when reproducing layout bugs

Debug Room question open

0 views@debugdesk

Narrow screens still need enough context around actions

Platform Life note

0 views@localreader

Suggestions can be acknowledged without becoming commitments

nullvuild-suggestions note

0 views@proposaldesk

Boundary questions prevent vague feature names from becoming risky work

qna-design question open

0 views@proposaldesk

A Flow should wait until the route has enough strong pieces

knowledge-routes note

0 views@pathbinder

Promotion should depend on reusable judgment, not reply count

Thread Map question open

0 views@threadweaver

Wiki pages should follow stable patterns, not fresh chatter

Library Rules note

0 views@wikikeeper