feat(neocode): establish NeoPi-first product identity and branding #59

Activity

1. PsychedelicShayna

   added

   enhancementNew feature or requestNew feature or request

   documentationUser- or agent-facing docs, README or changelogUser- or agent-facing docs, README or changelog

   priority: p2Useful planned workUseful planned work

   needs-triageNot yet triagedNot yet triaged

   difficulty: 0.375-0.500Estimated implementation difficulty in 0.375-0.500.Estimated implementation difficulty in 0.375-0.500.

   frame: hoursEstimated time frame: hours (agent estimates lowered one unit)Estimated time frame: hours (agent estimates lowered one unit)

   agent: startedAn agent has claimed this; do not duplicate the workAn agent has claimed this; do not duplicate the work

   and removed

   needs-triageNot yet triagedNot yet triaged

   on Oct 19, 2026
2. PsychedelicShayna commented on Oct 20, 2026

   

   PsychedelicShayna

   on Oct 20, 2026

   OwnerAuthor

   More actions

   Note

   GPT-6 Astra on behalf of PsychedelicShayna

   Installed nightly delivery: #108 merged as c9f91e00a43096e5f94e050627738b26bc7a0c9b, together with #107. The NeoCode desktop entry now launches ~/.local/lib/neocode/releases/v0.0.42-nightly.20261020.c9f91e00/squashfs-root/AppRun. Desktop-entry validation passed; the previous cf8f09db artifact and .desktop.before-c9f91e00 entry remain for rollback.

   Actual installed-app proof on the owned Xvfb :10, with normal shell hydration and private fixture state, not the owner's live database: launch succeeded; Settings → Providers is usable; NeoPi is first, enabled, authenticated and labeled NeoPi rather than NeoPi/OMP. The saved /home/shayna/.local/bin/npi-nightly path survived. Codex, Claude, Cursor, Grok, OpenCode and Antigravity remain disabled in this fixture. Both before/after screenshots were saved and visually inspected. The private app is left open.

   The installed server's --help says “Run the NeoCode server” and uses NeoCode in the app/pair/triage descriptions. Compatibility identifiers, the t3 command, t3.json, data paths, OMP launch compatibility and explicitly saved instance names remain unchanged. Upstream and external-service attribution remains explicit. No broader parity design was added.

   Focused verification: 120/121 tests passed initially across twelve files. The one old-brand wording assertion was replaced with the typed validation-error assertion; its isolated rerun passed (1 test, 8 skipped). The triage argv-safety test and throwaway canonical/embedded nightly-playbook check also passed. No full suite, Windows or native mobile execution is claimed. No new model turn or repeated session-restoration acceptance run was needed for these display changes.

   Installed AppImage SHA256: ec4683de9235ca3faa6c137494d4eeb598bbb09207489b5fc062e819b6645579. Embedded desktop version/commit match the installed source. Supported native caches were reused only after confirming native sources, lockfile and desktop package matched the prior artifact; build took 263.52 seconds. No NeoPi binary was rebuilt or installed.

   Evidence is saved under ~/.cache/npi-canary/mercury-108-delivery/: installed-identity-proof.json, installed-cli-proof.json, identity-before-providers.png, identity-after-providers.png. Public upload is pending the matching release run, whose Windows build was still running at the bounded watch deadline; this did not block installation. Public links will follow. Issue stays open until promotion to main.
3. PsychedelicShayna

   added

   agent: finishedThe agent's part is done; not necessarily mergeableThe agent's part is done; not necessarily mergeable

   and removed

   agent: startedAn agent has claimed this; do not duplicate the workAn agent has claimed this; do not duplicate the work

   on Oct 20, 2026
4. PsychedelicShayna commented on Oct 20, 2026

   

   PsychedelicShayna

   on Oct 20, 2026

   OwnerAuthor

   More actions

   Note

   GPT-6 Astra on behalf of PsychedelicShayna

   Public evidence is now attached to nightly release v0.0.42-nightly.20261020.39496593885.1. Its tag was verified directly against installed source c9f91e00a43096e5f94e050627738b26bc7a0c9b; the release workflow completed successfully.

   • Before · After
   • Installed GUI/artifact proof · Installed CLI proof
   • Exact locally installed AppImage · SHA256

   The locally installed AppImage is explicitly distinguished from the independently built CI AppImage. This completes the pending publication step; the earlier installed/private-state scope and verification limits still apply. The issue remains open with agent: finished until promotion to main.