| Age | Commit message (Collapse) | Author |
|---|
|
Break up the three most monolithic flat skills into a slim SKILL.md plus a
references/ directory of focused sub-files, matching the f3s and
agent-task-management structure. Pure reorganization: all content and meaning
preserved, only moved behind a reference index with resolving links.
- blog-writing-style (619->216): extract the Wikipedia-based 'Signs of AI
writing' deep catalog into references/signs-of-ai-writing.md.
- check-shopping-status (319->135): extract references/imap-scan-script.md
(steps 1-3 Python) and references/amazon-cdp.md (CDP login helper).
- photo-processing (232->155): extract references/auto-enhance.md (standalone
ImageMagick auto-enhance script).
Adds notes/skills-review-2026-06-19.md with the full inventory and the
follow-up task IDs (dq0, eq0, fq0) for the remaining oversized skills.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
Add references/r-node-deploy.md describing the Rex nfs_mount_monitor
rollout to r0/r1/r2: group/root/parallelism-3 conventions, idempotent
file/on_change reload flow, and systemctl/journalctl verification, so
conf-project agents don't re-derive the rollout each task. Wire it into
SKILL.md's reference index.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
Add a section on handling test suites that work but exceed the
go-test/mage/command timeout (e.g. mage integrationTest > 30m):
which focused subset to run (-short/-run/build tags, touched
packages), how to annotate that the full suite was intentionally
skipped, and the acceptance implications (focused subset is not
full verification). Cross-references the 8q0 missing-toolchain
section rather than restating it.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
Document how agents should handle a local toolchain that cannot build
or test the project (e.g. missing libbpf bpf/bpf.h headers, missing
flutter/dart). Preflight the build/test path before trusting it, run
the smallest verifying subset that works, annotate the blocker via
ask annotate, and never claim full verification that did not run.
Scoped to MISSING/incomplete toolchains; slow/long-running test suites
are covered separately by task 9q0.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
vendored/upstream deps
A sub-agent patched a vendored dependency (libbpfgo) and the change had to
be reverted. When completing a task appears to require changing a vendored,
generated, or upstream dependency, that is a scope boundary: flag it as a
blocker (annotate + report) instead of patching the dep. Added to
2-start-task.md with a pointer from SKILL.md; cross-references the
complete-task commit hygiene and stalled-worker recovery rather than
restating them.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
Extend the complete-task reference with a 'Commit only in-scope files'
section: at task start and before committing, run git status and split
dirty paths into in-scope vs out-of-scope (pre-existing/unrelated user
edits such as .gitignore/start.sh). Stage only in-scope files by explicit
path, never git add -A/. over a pre-existing dirty worktree, never commit
unrelated files, and record the in-scope/out-of-scope decision in an
ask annotate note. Cross-reference 6-recover-stalled-task.md (broken
partial WIP) to keep the two cases distinct and avoid duplication.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
Multiple ior/player tasks had a worker stall or get interrupted mid-edit,
leaving broken, uncommitted partial file edits with no documented recovery
path. Add references/6-recover-stalled-task.md covering detect -> assess ->
revert -> resume: how to spot a partial/interrupted edit (dirty worktree,
broken build, half-applied diffs), assess dirty changes against the task
annotations (keep in-scope WIP vs. discard broken edits vs. preserve unrelated
user changes), revert cleanly with scoped git checkout/stash WITHOUT destroying
unrelated work, then re-read annotations, resume from the last known-good
point, and annotate the recovery.
Wire the new reference into SKILL.md's 'When to load what' table and cross-ref
it from 2-start-task.md when picking up an already-started task. Commit
discipline is cross-referenced to 3-complete-task.md rather than duplicated.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
invocation contract
Agents repeatedly mistook `ask` for a natural-language interface and ran
things like `ask agent-task-management ...` or `ask <free text>`, forcing
orchestrators to paste the correction into every task description.
- Add a prominent STOP blockquote at the very top of SKILL.md stating that
`ask` is a CLI with fixed subcommands and that agent-task-management is a
skill name, never an `ask` subcommand.
- Add an explicit 'Invocation contract' section listing the only valid form
(`ask <subcommand> [args]`) and the real subcommands, derived from existing
content; consolidate the valid/invalid examples there (DRY) with inline
reasons on the invalid ones.
- Mirror the same STOP warning at the top of references/00-context.md and
tighten its rule to point at the contract.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
|
Documents the fishfinger/blowfish ProxyJump path to reach f-hosts
(paul + doas), r-VMs/rocky (root), and Pis from outside the LAN.
Notes the f3 WireGuard routing caveat and tcsh shell pitfall.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
Amp-Thread-ID: https://ampcode.com/threads/T-019ed908-ca57-7251-8ff1-ce10c8c3a787
Co-authored-by: Amp <amp@ampcode.com>
|
|
Amp-Thread-ID: https://ampcode.com/threads/T-019ed908-ca57-7251-8ff1-ce10c8c3a787
Co-authored-by: Amp <amp@ampcode.com>
|
|
Host-specific upload details now live in ~/git/worktime/.uprecords-sync.sh
(kept out of the public dotfiles repo). worktime::supersync calls it via
sh; f3s skill updated accordingly.
Amp-Thread-ID: https://ampcode.com/threads/T-019ed908-ca57-7251-8ff1-ce10c8c3a787
Co-authored-by: Amp <amp@ampcode.com>
|
|
- Implement worktime::uprecords::darwin::import: on earth, push the
Mac's uprecords files synced into the worktime repo to goprecords,
re-labelling host MBDVXJ4XKH9C -> mega-m3-pro.
- f3s skill: add k3s off-LAN remote-access reference (jump via OpenBSD
frontend -> root@r0.wg0 -> kubectl) and document the mega-m3-pro
upload config + earth GOPRECORDS_HOST gotcha in goprecords-uptimed.
Amp-Thread-ID: https://ampcode.com/threads/T-019ed908-ca57-7251-8ff1-ce10c8c3a787
Co-authored-by: Amp <amp@ampcode.com>
|
|
Amp-Thread-ID: https://ampcode.com/threads/T-019ed908-ca57-7251-8ff1-ce10c8c3a787
Co-authored-by: Amp <amp@ampcode.com>
|
|
Update the irregular.ninja refresh skill: the album moved to
~/git/irregular.ninja/irregular.ninja and is driven by shuriken (not the old
photoalbum/Makefile). Document the volatile cache/ directory (persistent EXIF
cache parallel to dist/, never deployed) and add a rule that only dist/ is
rsynced to the servers.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
extended-keys-format for tmux 3.2 compat
|
|
|
|
|
|
document LVM layout
|
|
f3 is now running node_exporter and is included in Prometheus
scraping alongside f0/f1/f2. Updated the skill reference to
reflect the new scrape config (192.168.2.133:9100) and include
f3 in the host list.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Tag names in the ask CLI do not support hyphens (-). Added a clear
note in both the rules section and the Conventions section of
1-create-task.md so agents use camelCase or concatenated words instead.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
|
|
|
|
creating-cd-mixes scripts
|
|
|
|
|
|
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
f0 sits at the bottom of the rack with a fan directly underneath,
so it consistently runs 10-15°C cooler than f1/f2 at the same load.
f1/f2 are higher up in warmer rising air with no dedicated airflow.
Do not use f0 as a baseline when comparing temps across hosts.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
Replace conservative guesses with actual data from Beelink S12 Pro
reviews and Intel N100 specs (TJmax 105°C, hardware throttle ~100°C).
Add a table with scenario/expected/action rows covering idle through
thermal throttle, plus real-world observations from 2026-05-17 across
all four f-hosts. Adjust remediation steps to match the revised
thresholds (investigate >80°C at moderate load; stop I/O at >90°C).
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
attribution
storage.md (942), k3s-setup.md (342), observability.md (273) split into
per-topic sub-files under references/<topic>/ with short index files at
the original paths.
Drops the SSD TRIM Configuration section added in 8d94f79 and reframes
the Thermal Troubleshooting cascade: the 2026-05-16 f0 incident was
thermal alone, not the multi-cause cascade (autotrim, zrepl interval,
encryption) the previous commit implied. Mitigations applied during
diagnosis are not what fixed it.
Other yesterday additions (zrepl DL-state recovery, CARP-when-ZFS-
suspended, ZFS SUSPENDED runbook, nfs-mount-monitor improvements) are
kept and routed to their respective sub-files.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
|
- observability.md: reflect current state — Grafana/Loki/Tempo disabled
(SQLite-on-NFS unreliable), Alloy running with minimal config only,
Prometheus TSDB wiped and restarted clean (2026-05-16 incident).
Add TSDB recovery runbook. Document .disabled manifest pattern.
- freebsd-setup.md: add coretemp kernel module section — all f-hosts
now have coretemp_load="YES" in /boot/loader.conf for persistent
per-core die temps (hw.acpi.thermal.tz0 is unreliable).
- hardware.md: add f3 IP (192.168.1.133) to LAN table.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
