chore: update opencode workflow and local config
This commit is contained in:
33
.memory/plans/fix-github-push-large-binary.md
Normal file
33
.memory/plans/fix-github-push-large-binary.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
title: fix-github-push-large-binary
|
||||
type: note
|
||||
permalink: dotfiles/plans/fix-github-push-large-binary
|
||||
tags:
|
||||
- git
|
||||
- risk
|
||||
- tooling
|
||||
---
|
||||
|
||||
# Fix GitHub Push Rejection for Large Binary
|
||||
|
||||
**Goal:** Remove the oversized `.local/bin/codebase-memory-mcp` blob from local-only history so `main` can push to GitHub successfully.
|
||||
|
||||
## Root cause
|
||||
- [decision] Commit `969140e` added `.local/bin/codebase-memory-mcp` at ~143.51 MB.
|
||||
- [decision] Commit `2643a0a` later removed the file, but the blob still exists in local history, so GitHub rejects the push.
|
||||
|
||||
## Tasks
|
||||
- [ ] Rewrite the 4 local-only commits by soft-resetting to `origin/main`.
|
||||
- [ ] Recreate a clean commit set without the large binary in history.
|
||||
- [ ] Verify no large-file path remains in reachable history.
|
||||
- [ ] Retry `git push` and confirm success.
|
||||
|
||||
## Acceptance criteria
|
||||
- No reachable commit from `HEAD` contains `.local/bin/codebase-memory-mcp`.
|
||||
- `git push` to `origin/main` succeeds without GitHub large-file rejection.
|
||||
|
||||
## Pre-mortem
|
||||
- Most likely failure: recommit accidentally stages a regenerated large binary again.
|
||||
- Fragile assumption: current worktree is clean except for the 4 local-only commits.
|
||||
- Red flag requiring redesign: if the large blob exists in earlier shared history, a broader history rewrite would be required.
|
||||
- Easy-to-miss regression: leaving `.local/bin/codebase-memory-mcp` unignored so it gets re-added later.
|
||||
43
.memory/plans/luks-sddm-kwallet-login-integration.md
Normal file
43
.memory/plans/luks-sddm-kwallet-login-integration.md
Normal file
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: luks-sddm-kwallet-login-integration
|
||||
type: note
|
||||
permalink: dotfiles/plans/luks-sddm-kwallet-login-integration
|
||||
tags:
|
||||
- auth
|
||||
- sddm
|
||||
- kwallet
|
||||
- luks
|
||||
---
|
||||
|
||||
# LUKS / SDDM / KWallet login integration
|
||||
|
||||
## Goal
|
||||
Configure the system so login feels unified across LUKS boot unlock, SDDM, and KWallet.
|
||||
|
||||
## Clarified scope
|
||||
- [decision] User selected **Password login** instead of true SDDM autologin because password login preserves KWallet PAM unlock.
|
||||
- [decision] User selected **Just document commands** instead of expanding repo scope to manage `/etc` files directly.
|
||||
- [decision] Deliverable is repo documentation with exact manual system commands/edits; no tracked `/etc` files will be added in this change.
|
||||
|
||||
## Discovery
|
||||
- Dotfiles repo contains user-space config only; system auth files live outside the repo.
|
||||
- Current system already references `pam_kwallet5.so` in `/etc/pam.d/sddm` and `/etc/pam.d/sddm-autologin`, but the module is missing and silently skipped.
|
||||
- `kwallet-pam` is available in Arch repos and should provide the current PAM module for KWallet 6.
|
||||
- LUKS unlock and SDDM login are independent phases; there is no direct password handoff from initramfs to SDDM.
|
||||
- True SDDM autologin conflicts with password-based KWallet unlock because no login password is available to PAM during autologin.
|
||||
|
||||
## Tasks
|
||||
- [ ] Write documentation for package install and PAM edits needed for SDDM/KWallet integration
|
||||
- [ ] Document wallet initialization and verification steps
|
||||
- [ ] Review documentation for correctness and scope alignment
|
||||
- [ ] Validate documented commands against current system state where possible
|
||||
- [ ] Check documentation coverage/placement in repo
|
||||
|
||||
## Acceptance criteria
|
||||
- README documents the exact package install step and the exact PAM module substitutions needed.
|
||||
- README explicitly states that password login is the chosen model and true SDDM autologin is not part of this setup.
|
||||
- README includes KWallet initialization and verification steps suitable for this Arch + Hyprland + SDDM setup.
|
||||
- Reviewer/tester/librarian passes are recorded before completion.
|
||||
|
||||
## Workstream
|
||||
- Single workstream in the main repo working tree.
|
||||
37
.memory/plans/tmux-shift-enter-fix.md
Normal file
37
.memory/plans/tmux-shift-enter-fix.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: tmux-shift-enter-fix
|
||||
type: plan
|
||||
permalink: dotfiles/plans/tmux-shift-enter-fix
|
||||
tags:
|
||||
- tmux
|
||||
- terminal
|
||||
- keybindings
|
||||
---
|
||||
|
||||
# tmux Shift+Enter Fix
|
||||
|
||||
## Goal
|
||||
Inside tmux, pressing Shift+Enter should insert a literal newline instead of submitting the command line.
|
||||
|
||||
## Decision
|
||||
- [decision] Preserve tmux extended-keys support and apply the smallest possible fix at the tmux layer.
|
||||
- [decision] Use `bind-key -n S-Enter send-keys "\n"` in `~/.tmux.conf` instead of disabling `extended-keys` or adding shell-specific bindings.
|
||||
|
||||
## Tasks
|
||||
- [ ] Add a tmux root-table binding for `S-Enter`
|
||||
- [ ] Verify tmux loads the config and exposes the expected binding
|
||||
- [ ] Check documentation coverage for this config tweak
|
||||
|
||||
## Acceptance criteria
|
||||
- `~/.tmux.conf` contains an explicit `S-Enter` binding that sends a newline.
|
||||
- Existing `extended-keys` settings remain enabled.
|
||||
- After sourcing the config, tmux shows the `S-Enter` root binding.
|
||||
|
||||
## Workstream
|
||||
- Single workstream in the main repo working tree.
|
||||
|
||||
## Findings tracker
|
||||
- None.
|
||||
|
||||
## Relations
|
||||
- related_to [[knowledge]]
|
||||
Reference in New Issue
Block a user