Zenmemes meta feedback summary

Feedback from 24 imported threads carrying the meta board tag or thread label, including all 129 root posts and replies (36 automated reply-agent posts). The source dates run from 2026-04-13 through 2026-10-17. Repeated requests are merged below; the source inventory lists every included thread.

Scope is the locally available Zenmemes content accepted or already present in the latest import report. That import was partial, so rejected or conflicting source content is not covered. Unlabeled threads are outside this summary. Reported behavior is historical feedback. Status markers below reflect a targeted local code/documentation review on October 19, 2026, not a production or physical-device audit. Unverified items remain open.

Railspike cycle estimates use an uncapped scale from 0 upward, including decimals. Estimates are retained from the original inventory; they are not remaining-work estimates.

Feature requests

Bug reports

Unless marked otherwise, these reports have no explicit resolution in their thread.

Local implementation progress (2026-10-19)

• Feature 25: ordinary clicks on the thread root Reply link expand, focus, and scroll to the inline composer. The dedicated reply URL remains available through modified clicks, middle-click, opening the link separately, and the no-JavaScript fallback. node tests/browser/inline_reply_link.mjs passed at 390px and 1280px, covering scroll/focus, draft preservation, uncancelled modified clicks, a real middle-click/new-tab navigation, and no-JavaScript navigation. JavaScript/PHP syntax and diff checks passed. Physical-device verification remains open.

• Bug 01: disabled automatic capitalization on the Board tags input (commit 392f43bc). PHP syntax and diff checks passed; mobile device verification remains open.

• Bug 02: theme cycling skips modes that resolve to the current appearance; explicit menu selection still permits Auto/System and Light separately. node tests/browser/theme_cycle.cjs covers light/dark system preferences, the next-theme label, persistence, checked options, wraparound, explicit selection, and equivalent-only choices. All 11 ThemeRegistryTest tests, JavaScript syntax, and diff checks passed. Visual browser verification remains open.

• Bug 07: reproduced remaining wrapping with the current actions menu: the submit button inherited width: 100%, pushing the menu to another row. Giving that button automatic width keeps both controls on one row. node tests/browser/reply_actions_layout.mjs passed 20 Chromium combinations (320/375/390/480/768px; Light, Word 97, Chicago, Midnight), checking alignment, overlap, touch-target heights, menu opening, and horizontal overflow. Existing compose_disclosure.mjs checks and diff checks also passed. Physical mobile-device verification remains open.

• Bug 03: compose normalization now restores cursor position and selection direction, adjusting selection offsets when text expands or is removed. Regression coverage includes a smart quote in the middle of a draft, punctuation expansion, unsupported-character removal, and unchanged text. All 82 BrowserSigningNormalizationTest tests, JavaScript syntax, and diff checks passed. Device verification remains open.

• Feature 33: removed the generic browser-identity notice from pending reply cards and omitted the metadata row when no author label exists. Available author labels and posting status remain. Four targeted pending-reply renderer/submission/recovery checks and JavaScript syntax passed.

Resolution evidence and remaining scope

• Feature 03: the new-member review explains conduct/integrity responsibility; one-click pending approval was deliberately retained in the follow-up. This is not a new confirmation requirement.

• Feature 08: the existing notification feature flag supplies the requested toggle; Bug 05 stays open because its unspecified underlying failure has not been reproduced or certified fixed.

• Features 28–30: current reply compose renders the parent body; SQLite Viewer links the downloadable read model and query pack and offers preset queries; Word 97, Chicago and Midnight are among the available classic themes. These closures describe repository behavior, not a fresh production test.

• Bug 10: startup dependency recovery records missing-runtime/extension and refusal/retry checks on Ubuntu 22.04 and 24.04. This does not certify every platform or terminal/PATH setup.

• Bug 11: commit 0d3f78e1 fixes selected-nav specificity; the completion record reports browser cascade checks across all themes and live Word 97/Midnight navigation checks. The broader button/collision audit was not completed and remains separate follow-up.

• Existing local progress notes retain their mobile/device and visual verification gaps. Performance, historical data freshness, iPhone keyboard behavior, and unverified feature requests remain open; an adjacent improvement is not evidence of full resolution.

Other

Automated suggestions and disagreements

Automated replies often restate requests, ask for reproduction steps, or propose implementation details. Their statements about flagging, profiling, delivery milestones, or implementation are not evidence that work happened.

• Agent-only proposals include broad button sets (Submit/Save/Cancel, reset/undo/navigation/help/bulk actions), accessibility improvements, progressive enhancement, filter preference memory, clipboard fallbacks, transient copy feedback, per-thread or email notifications, privacy controls, local recent-history storage, and optimistic UI with rollback. These are suggestions rather than additional user requirements.

• The agent interpreted Clear identity as temporary anonymity; the original request does not establish that behavior. It interpreted the new-version feature as a new UI release; the original does not specify that. Its response to key-pair preservation asked about generic form/data keys, leaving the actual request unresolved.

• The agent opposed empty or whitespace-only submissions, opposed restricting bad votes to approved users, suggested an optional theological persona, and preferred per-thread verbosity controls over minimizing all agent replies. Those disagreements do not override the user requests above.

• The agent suggested opt-out tags such as agentless and no-agent-replies, but its later list of 15 generic tags did not answer the naming follow-up. No tag choice was settled.

• The compose-context reply proposed highlighting, auto-scrolling, and pinning quoted text; the SQLite reply asked for schema/query/UI details. Neither establishes agreed implementation scope.

• Remaining automated comments acknowledge bugs, discuss tone and community rules, or summarize the Word 97 report without adding a distinct user request.

Source inventory

Each count includes the opening post. Sources link to the imported instance; the corresponding raw records remain under state/local_repository/records/posts.