chore: copy across cat pool spec from celestia-core

[cmwaters]

Overview

Given that it is only the specification of celestia-app that is published it makes more sense to include it there rather than in the directory of the cat pool itself

Checklist

• New and updated code has appropriate documentation
• New and updated code has new and/or updated testing
• Required CI checks are passing
• Visual proof for any user facing features like CLI or documentation updates
• Linked issues closed with keywords

[github-actions]

PR Preview Action v1.4.4
🚀 Deployed preview to https://celestiaorg.github.io/celestia-app/pr-preview/pr-2207/
on branch gh-pages at 2023-08-07 09:12 UTC

[codecov-commenter]

Codecov Report

Merging #2207 (7937bc1) into main (772d0b8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2207   +/-   ##
=======================================
  Coverage   24.89%   24.89%           
=======================================
  Files         127      127           
  Lines       14335    14335           
=======================================
  Hits         3568     3568           
  Misses      10400    10400           
  Partials      367      367           

[rootulp]

LGTM. In the past there was a push for specs to live in the same repo as the code they are relevant to. If we still want that, we can alternatively consider publishing celestia-core specs to their own website so that they don't need to be copied to celestia-app. I'm curious what @adlerjohn thinks.

[rootulp]

I think we may want to add this to the README here:

celestia-app/specs/src/README.md

Line 7 in 492c3db

- [Consensus](./specs/consensus.md)

It's a bit ridiculous to maintain 3 locations for the same table of contents so we may consider deleting that README alltogether.

[cmwaters]

Yeah I added it to the SUMMARY.md which I think is the main one in terms of the rendered static site

[evan-forbes]

In the past there was a push for specs to live in the same repo

alternatively we could simply link to the catpool spec in core. all that matters imo is that we have a single starting place that at least links to everything.

[cmwaters]

I tend to agree that they should live in their own repo but its a bit strange when it comes to forks. I would also prefer that from the outside Celestia is presented as a single cohesive spec

[staheri14]

Looks good! I'd recommend removing the original spec from the cat pool directory and adding a link to this one to avoid having multiple copies.

Update: I see that the cat pool lives in the core repo, so, it may as well make sense to have a separate website dedicated to the core related specs. Though no strong opinion.

[cmwaters]

it may as well make sense to have a separate website dedicated to the core related specs

Ideally I'd like to have a single site that contains all the specification of the celestia network (including celestia-node as well). For now, to make it more visible, I think it's better here and once we develop a better system we can remove it and just have a spec directory in core