Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

redesign(brainbar): confine DEV previews to a fixed non-configurable root

Open
  • Is something wrong?
#897 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
build-system, desktop, security

Research direction

Start by tracing the DEV build interface and BrainBarDevHarnessCommit, then review the #894 B6/B7b, B9, B10, and B11 destination probes. Map the Preview Settings UI and action layers, identity validation, and harness stamping before changing behavior. Done means the listed acceptance checks pass, including independent behavioral oracles and refusal of malformed or stale targets.

Written by the indexing model from the issue text.

Description

Why

#894 was blocked eight times by production-reachable hazards. Fixing individual path checks repeatedly exposed another bypass: direct production destinations, canonical equivalents, nested app paths, symlinks through nonexistent intermediates, and case variants. That is a design failure, not a finite blacklist to extend.

Required design

  • Remove BRAINBAR_DEV_APP_DIR and every caller-controlled destination override.
  • Compute preview destinations internally beneath one fixed, non-configurable DEV root.
  • Make arbitrary production, resident, nested, symlinked, case-varied, and non-existent-intermediate destinations structurally unrepresentable rather than guarded one by one.
  • Keep previews UI-only and prevent Settings from reaching the production ~/.config/brainlayer/brainlayer.env write path.
  • Treat any com.brainlayer.brainbar.dev.* identity with missing or malformed preview metadata as refusal, never production.
  • Ensure BrainBarDevHarnessCommit identifies the harness code that actually built the bundle; refuse or overlay stale target harness files.

Acceptance

  • No destination override exists in the DEV build interface.
  • Every DEV output is demonstrably a descendant of the fixed DEV root.
  • The #894 B6/B7b destination probes are impossible through the public interface and remain mutation-pinned.
  • Preview Settings are inaccessible at both UI and action layers.
  • Malformed DEV identity cannot start production integrations, server behavior, watchdogs, hotkeys, URL handling, or BrainBus.
  • A target with stale harness files cannot receive a current harness stamp.
  • All tests use independent behavioral oracles; stamp values are never checked only against their own inputs.

Reference: #894, especially B6, B7b, B9, B10, and B11.

— brainlayerCodex (worker) · codex/gpt-5.6-sol

Dominant language
Python
Stars
9
Forks
7
Avg merge
4h 30m
Merged PRs (30d)
392

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EtanHey/brainlayer

All issues in EtanHey/brainlayer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.