natsukium/felis
Watch
1
Code Issues 27 Pull requests 1 Projects Releases Packages Wiki Activity Actions

[Post-v0.1/P2] Retire temporary redesign transfer logs #34

New issue
Closed
opened 2026-09-03 16:18:10 +09:00 by natsukium · 1 comment
natsukium commented 2026-09-03 16:18:10 +09:00
Owner
Copy link

Follow-up from #12 (P2); run after all accepted pre-release decisions are recorded.

Why

The felis-redesign-*.md files are transfer logs, not a durable decision layer. Keeping them after their decisions land would create a second source of truth alongside the reference/explanation twins.

Scope

  • Trace every accepted decision to its owning explanation page and normative reference twin.
  • Move user-visible history to CHANGELOG.md where needed.
  • Remove the transfer logs only after a repository-wide citation and terminology sweep.

Acceptance criteria

  • No unique active requirement or rationale exists only in a transfer log.
  • References to removed files are eliminated.
  • docs/README.md remains the complete documentation map.
  • A docs-wide grep sweep confirms terminology and links are consistent.
Follow-up from #12 (P2); run after all accepted pre-release decisions are recorded. ## Why The `felis-redesign-*.md` files are transfer logs, not a durable decision layer. Keeping them after their decisions land would create a second source of truth alongside the reference/explanation twins. ## Scope - Trace every accepted decision to its owning explanation page and normative reference twin. - Move user-visible history to `CHANGELOG.md` where needed. - Remove the transfer logs only after a repository-wide citation and terminology sweep. ## Acceptance criteria - [ ] No unique active requirement or rationale exists only in a transfer log. - [ ] References to removed files are eliminated. - [ ] `docs/README.md` remains the complete documentation map. - [ ] A docs-wide grep sweep confirms terminology and links are consistent.
natsukium commented 2026-09-03 16:28:46 +09:00
Author
Owner
Copy link

Completed by 5077d74b. The transient review files are gone, their actionable findings are tracked in #12–#33/#35, and a repository-wide grep finds no remaining references.

Completed by 5077d74b. The transient review files are gone, their actionable findings are tracked in #12–#33/#35, and a repository-wide grep finds no remaining references.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
ci/darwin-smoke
No results found.
Labels
Clear labels   
priority/P0
Must be resolved before the v0.1.0 tag

  
priority/P1
Must be settled before the first public contract freezes

  
priority/P2
Explicitly deferred until after v0.1.0

  
release/v0.1.0
Work tracked for the first tagged release

  
status/blocked
Cannot start now: waits on an upstream release, another issue, or a recorded revisit trigger

  
status/planned
Triaged with a source-grounded plan and a passed pi review; ready to implement

  
type/bug
Shipped behavior that contradicts the docs or the code's own intent; needs a product code change

  
type/design
An open scope or trade-off question; needs a recorded decision in the owning explanation doc before code

  
type/test-gap
Documented or reviewed behavior that no test pins; usually split from a review finding, needs no product code change

  
type/tracker
Parent issue that tracks child work

No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
natsukium/felis#34
No description provided.