[bug] TELOS summary marks [x] goals completed, ignores dropped

Open Beginner friendly
  • Is something wrong?
#2,606 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 9 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
backend

Research direction

Start with GenerateTelosSummary.ts and trace parseGoals into bucketOfItem to see how itemText, body, and status markers determine each goal’s bucket. Reproduce the two reported shapes in a fixture or the existing tests, then verify ticked sub-items do not complete a goal and dropped goals are omitted from the summary.

Written by the indexing model from the issue text.

Description

What happened

TELOS summary marks [x] goals completed, ignores dropped

Summary

GenerateTelosSummary.ts (parseGoals → bucketOfItem) misclassifies goals in the unified TELOS.md:

  1. A ticked progress sub-item in a goal's body ("- [x] step") files the whole goal under "Completed", because CHECKBOX_COMPLETED is tested against itemText + body.
  2. A dropped goal ("### G0: … — DROPPED", "Status: Dropped") still renders as Active: DROPPED is not in any token or status set, so it falls back to the section heading's Active bucket.

Suggested fix (tested locally on a fixture reproducing both shapes):

  • Test CHECKBOX_COMPLETED against itemText only.
  • Add a dropped marker set: uppercase tokens (DROPPED, RETIRED, ABANDONED, CANCELLED) and Status values (dropped, retired, abandoned, cancelled). When either matches, return null so the goal is left out of the summary; check this before the completed/deferred rules.

Details

  • Kind: bug
  • LifeOS version: 8.761.0

Filed with the LifeOS /feedback command. The reporter approved this exact text before it was sent; paths, secrets and personal details were stripped locally.

Dominant language
TypeScript
Stars
19.7k
Forks
2.5k
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 danielmiessler/LifeOS

All issues in danielmiessler/LifeOS

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.