Project Tracker

Project Tracker

Every open task: a bug to fix, an improvement to make, an investigation to close. Nothing here is a promise or a supported feature. History, measurements and lessons live in Engineering Notes, the Changelog, and the repository's docs/. The table follows docs/task-table-standard.md.

Tasks

ID	Task	Type	Area	Size	Status	Owner	Next step
TT-035	Memory keeps an amended fact beside the original when consolidation names it under a new key	Bug	Memory	M	Open	here	On contract, session 1 distilled the agreement under mga/* (mga/governing_law=england, mga/termination_notice_days=60, mga/sub_processors_permitted=true); session 2 put the amendment under a second prefix (msa/calder/* in the first pass, msa/* then agreement/* in the three-run set) and later sessions distilled 1/0/0/0 facts, so no key ever matched and supersession could not fire — both values stayed live and the model answered with either. Three runs per arm: memory carryable 67/71/46% (mean 61.3) and foundation 33/33/83% (mean 49.7) against the summary's 75/54/79% (69.3) and 67/58/67% (64.2); stale 15 vs 16. The defect is structural in the logs and noisy in the score. Decide between entity resolution across key prefixes and a consolidation instruction that must reuse an existing address, and pin it with a two-session test. Evidence: docs/master-benchmark-results.md; logs under .build/benchmark-logs/memory-contract-qwen36-4bit/ (not committed)
TT-018	plugins/dsh-tinytitan is not published	Chore	Harness	M	Blocked	operator	The catalogue half is done: PR #5396 merged 2026-09-19 by fkysly (merge commit 4d136c1), so dsh-tinytitan is in the catalogue. Remaining: the npm publish, the operator's account. The Pummelchen/awesome-dsh-plugin fork is now inert and cannot be deleted from this checkout — the token lacks delete_repo — so either gh auth refresh -h github.com -s delete_repo or remove it in the web UI
TT-020	The LAN Manager cannot be reached from another machine	Improvement	Harness	—	Blocked	upstream	Discussion #7111 answered 2026-09-19 by PerryLink: the gate is the webserver's schema, which admits exactly 127.0.0.1 and 0.0.0.0 (packages/host/webserver/src/index.ts:126), not the CLI guard — that one refuses only the wildcard, so an interface literal passes it and dies at validation. A specific-interface bind would also need its address folded into resolveLanTrust's trustedHosts, which branches on the wildcard. Upstream's call: a LAN bind changes reach, not the credential, since /api already requires the launch token's signed cookie. Workaround today: an SSH launch, or a tunnel to loopback