[custom] Port StarIntel research dashboards, approvals, TODO sync, capture, and activity tools #5

New issue

Open

opened 2026-09-16 04:13:22 +00:00 by nsaspy · 0 comments

nsaspy commented

2026-09-16 04:13:22 +00:00

Owner

Parent: #1

RAGE contract

Consume only this issue on rage/<issue>-<slug>. Initialize the run log with the canonical RAGE helper and preserve the immutable full start SHA. Load the canonical rage and adadr skills from lost-rob0t/skills before architecture or implementation. Blocked by the control-plane decision in #2.

Queue blockers: #11

Analyze

Cover research-approval, research-dashboard plus evil/local variants, starintel.el, starintel-research.el, gpt-todos, screen-capture, activity-watch, and their existing ERT tests.
Identify service boundaries and preserve current authorization semantics.

Gate

Research approval and task state remain durable and fail closed.
Capture tools must make target, output path, and privacy boundary visible.

Execute

Port each custom feature as a tested Lem/Common Lisp module or explicit service client.
Keep business logic separate from frontend rendering and keymaps.

Evaluate

Translate behavioral fixtures and run approval, pagination, offline, stale state, malformed service response, capture failure, and activity-service absence tests.
Compare against pinned Emacs tests.

Recurse

If a custom module actually belongs to another repository/service, record and approve that ownership move before implementation.

Acceptance

Custom daily workflows have durable owners and tests.
Offline/missing-service states do not brick Lem.
Approval decisions are auditable.

Durable evidence

Update the relevant facts in .prolog/kb/lem_migration.pl and .prolog/kb/issues.pl in the same change.
Record focused red/green evidence, the full local gate, packaging checks, and exact-head CI status.
Keep failed iterations and architecture contradictions visible.

Stop conditions

Authorization semantics are weaker than source.
Personal data would be committed.
Ownership boundary is unresolved.

Parent: #1 ## RAGE contract Consume only this issue on `rage/<issue>-<slug>`. Initialize the run log with the canonical RAGE helper and preserve the immutable full start SHA. Load the canonical `rage` and `adadr` skills from `lost-rob0t/skills` before architecture or implementation. Blocked by the control-plane decision in #2. Queue blockers: #11 ## Analyze - Cover research-approval, research-dashboard plus evil/local variants, starintel.el, starintel-research.el, gpt-todos, screen-capture, activity-watch, and their existing ERT tests. - Identify service boundaries and preserve current authorization semantics. ## Gate - Research approval and task state remain durable and fail closed. - Capture tools must make target, output path, and privacy boundary visible. ## Execute - Port each custom feature as a tested Lem/Common Lisp module or explicit service client. - Keep business logic separate from frontend rendering and keymaps. ## Evaluate - Translate behavioral fixtures and run approval, pagination, offline, stale state, malformed service response, capture failure, and activity-service absence tests. - Compare against pinned Emacs tests. ## Recurse - If a custom module actually belongs to another repository/service, record and approve that ownership move before implementation. ## Acceptance - [ ] Custom daily workflows have durable owners and tests. - [ ] Offline/missing-service states do not brick Lem. - [ ] Approval decisions are auditable. ## Durable evidence - Update the relevant facts in `.prolog/kb/lem_migration.pl` and `.prolog/kb/issues.pl` in the same change. - Record focused red/green evidence, the full local gate, packaging checks, and exact-head CI status. - Keep failed iterations and architecture contradictions visible. ## Stop conditions - Authorization semantics are weaker than source. - Personal data would be committed. - Ownership boundary is unresolved.

nsaspy referenced this issue

2026-09-16 04:13:23 +00:00

[org] Port Org, Org-roam, agenda, capture, Babel, alerts, and publishing #11

nsaspy referenced this issue

2026-09-16 04:13:23 +00:00

[epic] Port the complete active Emacs environment to Lem #16

nsaspy referenced this issue

2026-09-19 02:57:04 +00:00

[starintel-ide] Compose Lem SDL2, Quasar, A2A, STAR-KB/spec IDE, Git and LLM UX #17